Comment 0 for bug 407419

The Ball implementation is not framerate independent; it is based on a describe number of steps (fixed at 10 right now). That means that changing the target FPS constant in Constants.py will effectively change the speed of ball movement.

A better idea is if the balls move with a certain number of pixels per second. Then any target FPS could be set, even dynamically at boot time (eg. to target the same FPS as the current desktop resolution refresh, for smoothest possible experience).