This is for folks who may have a continuing interest in the topic. While trying to use GameClock I discovered a bug. While I was in there a-squashing, I added a couple methods. Then I decided to take the prediction demo to the next level and solve the screen-edge rebound problem, with plenty of here's-why-and-how notes.
These are available at game_clock.py<http://code.google.com/p/trollsouttaluckland/downloads/detail?name=game_clock.py&can=2&q=>and pygame.org/wiki/ConstantGameSpeed<http://www.pygame.org/wiki/ConstantGameSpeed> . Gumm
