nanogui: (apparently) strange event loop behaviour


Previous by date: 5 Dec 2000 21:01:35 -0000 (apparently) strange event loop behaviour, Darin J. Nelson
Next by date: 5 Dec 2000 21:01:35 -0000 nano-x production version, Gray, Tim
Previous in thread: 5 Dec 2000 21:01:35 -0000 (apparently) strange event loop behaviour, Darin J. Nelson
Next in thread: 5 Dec 2000 21:01:35 -0000 Re: (apparently) strange event loop behaviour, Darin J. Nelson

Subject: Re: (apparently) strange event loop behaviour
From: "Greg Haerr" ####@####.####
Date: 5 Dec 2000 21:01:35 -0000
Message-Id: <0cb801c05efe$dc69cfc0$15320cd0@gregh>

: timer event as well.  Problem is that my screens don't seem to update 
: when using GrGetNextEventTimeout.  Everything else looks right in the 
: code.  I'm basically using a couple of offscreen windows, and when one 
: taps/clicks on a tab-like-thingy to change the 'mode', I switch the 
: exposed window with GrCopyArea.

I assume that everything except for the clock works perfectly
when not using the GetNextEventTimeout.  If not, my response
won't apply.

There is a small possibility that your application is falling prey to
the bug that we just fixed in 0.89pre7 (to be released hopefully tonight).
In this case, if you return from a GetNextTimeout w/o timeing out,
and then you execute another GrXXX call, you may lose events,
and it sounds like you're losing the expose event.  Try commenting
out any draw/server calls during timeout processing.  If that fixes
the problem, then my client.c fix should fix this problem as well.

Regards,

Greg



Previous by date: 5 Dec 2000 21:01:35 -0000 (apparently) strange event loop behaviour, Darin J. Nelson
Next by date: 5 Dec 2000 21:01:35 -0000 nano-x production version, Gray, Tim
Previous in thread: 5 Dec 2000 21:01:35 -0000 (apparently) strange event loop behaviour, Darin J. Nelson
Next in thread: 5 Dec 2000 21:01:35 -0000 Re: (apparently) strange event loop behaviour, Darin J. Nelson


Powered by ezmlm-browse 0.20.