As I mentioned, the polling turned out to be acceptable in terms of CPU hit. The process would wake up every 100 msec, check for an event, then block again so it really didn't tie things up too badly. Still, I found a different approach.
Thanks for all the input! Cheers, Gil -----Original Message----- From: Kees Schoenmakers [mailto:[EMAIL PROTECTED] Sent: Monday, September 08, 2008 3:02 AM To: nanogui@linuxhacker.org; Greg Haerr Cc: Gil Glass Subject: Re: [nanogui] Difficulty Using GrInjectKeyboardEvent() On zaterdag 6 september 2008, Greg Haerr wrote: > : This makes the application active contineously while checking for events > > to > > : handle when it has time to. > > The problem with this approach is that the application polls and uses > cpu time continuously. This may work if only one application is running > but quickly becomes a bad design if multiple applications run using > the same approach. > > Regards, > > Greg > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] Hi, It is just _one_ application that does a lot of things and as part of that it update data to be displayed and resfresh the display. Kees --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
