On 4 May 2013 00:42, Ian Kelly <ian.g.ke...@gmail.com> wrote: > The other thing that is suspicious about the code you posted is that > it has two different notions of the ball's position that are not > necessarily in agreement. There is the ball_rect, and there are also > the x and y variables.
<snip> > You should be careful to make sure these > variables agree at all times -- or better yet, get rid of x and y > entirely, so that you only have one notion of the ball's position to > worry about. Pygame uses integers for its Rects and thus I advise much the opposite: *never* store position in Rects. Sorry, but it's true. You'll need to keep x and y around and try to use Rects only when representing pixels on the screen. Pygame has a lot of deficiencies with its default set of objects and functions, so it's something to get used to.
-- http://mail.python.org/mailman/listinfo/python-list
