On 15 Jul, this message from [EMAIL PROTECTED] echoed through cyberspace: [snip] > Perhaps there would be value to a motion rate limiting option in the X > server. This is not merely covering up for flawed applications. In the > current environment, a fast application can respond to the XMotionEvent > faster than the events are sent. So the fast application is performing > the cycle of read an event, update the screen, and returning to read > another event several times per screen refresh. This is waste motion > and interferes with scheduler logic. It would make sense to specify to > the X server that it should combine motion events for 10-20 milliseconds > before sending another motion event. This avoids all the scheduling and > messaging traffic during that invisible interval.
Hmm... sync the events to a VBL interrupt? Cheers Michel ------------------------------------------------------------------------- Michel Lanners | " Read Philosophy. Study Art. 23, Rue Paul Henkes | Ask Questions. Make Mistakes. L-1710 Luxembourg | email [EMAIL PROTECTED] | http://www.cpu.lu/~mlan | Learn Always. " _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
