From: Dave M. <mo...@ni...> - 2000-05-24 09:52:51
|
For the record, today I found a XF86 FAQ entry suggested renicing X to -10. That unsticks the mouse, even if I'm drawing graphics as fast as possible. Dave Morse writes: > I'm experiencing some bad behavior in a game I'm writing. > > My problem is that if Mesa draws my scene faster than 30 Hertz then I > never get any x events. So as far as my client can tell, the mouse never > moves again. > > All other applications recieve X events normally. > > If I comment out the Mesa drawing code, then I get X events normally. > > During the locked times, top reports that X is consuming 90% cpu time. > > My machines are K6/450 and PII/333 running software mesa 3.3 beta. > > Can someone explain why X is so studiously ignoring the event sending half > of its job, in favor of the rendering half? > > Any ideas for a solution? |