nanogui: Problem With GrGetNextEventTimeout()?
Subject:
RE: [nanogui] Problem With GrGetNextEventTimeout()?
From:
"Gil Glass" ####@####.####
Date:
14 Nov 2006 16:29:01 +0000
Message-Id: <6ECE57DF49376146B91A92A3C37EFC0E02546FF6@SJEXCH03.ds.jdsu.net>
Aha! It looks like, in my config file, VTSWITCH=Y! Changing it to 'N'
fixes the problem. I'm not sure why I would have done this in the first
place. Can you briefly explain what "VTSWITCH" means?
Thanks for looking into this!
Cheers,
Gil
-----Original Message-----
From: Greg Haerr ####@####.####
Sent: Monday, November 13, 2006 1:26 PM
To: Gil Glass; ####@####.####
Subject: Re: [nanogui] Problem With GrGetNextEventTimeout()?
> Now, I'm calling GrGetNextEventTimeout() with
a value of 1000 ms BUT THERE APPEARS TO BE ANOTHER TIMER WITH A TIMEOUT
OF BETWEEN 49 OR 50 ms (and sometimes 1 ms and sometimes 7 ms and
sometimes others) THAT CONSISTENTLY TRUMPS MY 1000 ms TIMEOUT TIMER.
Linux's select() function is then called with this much shorter timeout
and, even though there's no event, a GR_EVENT_TYPE_TIMEOUT event is not
generated.
Hmmm... Make sure VTSWITCH=N, since the
drivers/vtswitch.c code calls GdAddTimer to deal
with changing consoles when drawing. You might
also grep for GdAddTimer and find any other
code that might create a timer.
For debugging, perhaps add some printf() code in
the addtimer routine so you'll know what timers are
being created.
Keep me posted, we'll get this fixed
Regards,
Greg
,
