Eating surplus events?




Hiya

A window in an application I'm writing allows the user to interact with it by
moving the pointer over it.

I use the motion_notify_event_impl() virtual function to capture the movement of
the mouse, and update the display each time a motion_notify event is
received.  This works fine, however there is the problem that so many
motion_events are queued that it can take a while to process the backlog.

Is there a function to 'eat' the surplus events, say at the end of each call
of motion_notify_event_impl()?  Are there any other ways to limit the number
of motion events created?

C-YA
Jon

http://www.dookie.demon.co.uk



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]