SetTimer problems under XP

SetTimer() means your program gets WM_TIMER windows messages.

These messages are lower priority than most other messages (such as those for mouse movement etc).

That means that messages with a higher priority always take precedence in the message queue for your window (i.e. a mouse message will "jump the queue" and push your WM_TIMER message to the back).

This means that the more "other" messages your application is recieving, the lower the priority consideration your timer messages will get, so they may take a lot longer to "arrive" at your program than you hoped.

WM_TIMER is the least precise way of doing timing. You shouldn''t really use it for anything that NEEDS precise updates (such as animation in a game). I''d only really use it for doing things like updating low importance animations in a Windows application (stuff like the animation you get when a file is downloading - unlike a game, you don''t care if the animation stutters or slows down because it''s not the main focus of what you''re doing).

--
Simon O''Connor
Creative Asylum Ltd
www.creative-asylum.com

Awesome, that''s all I needed to know ; )

Thanks a lot.