nanogui: Thread: GrCheckNextEvent Modifications?

Greg at al,

Between Pre2 and Pre4 have any modifications been made to the way
GrMainLoop & GrCheckNextEvent - Code that worked fine (and still does)
when linked against Pre2 (example below) ceases to function when linked
against Pre4.

If the #if is set to 1 then the code functions partially then dies with
a GrRead error.  I was just wondering if there was any changes that
could effect the way my code is working....

Interesting enough, nterm.c gets the same problems (the read error) when
compiled against Pre4, and that uses GrMainLoop, IIRC.

----[ code snip ]----
#if 0
   GrMainLoop(HandleEvent);
#else
   while(1) {
      GR_EVENT ev;

/*	cycle_poll(main_loop)    */
      GrCheckNextEvent(&ev);
      HandleEvent(&ev);
   }
#endif
----[ end code snip ]----

	-Darran

--
 Darran D. Rimron            European Research & Development Manager
Real Data Services, 117-119 Marlborough Road, Romford, Essex, RM7 8AR
 ####@####.####                      http://www.getreal.co.uk/
 Phone:44-1708-70-44-33 Fax:44-1708-74-88-59 Mobile:44-7931-37-59-39

: Between Pre2 and Pre4 have any modifications been made to the way
: GrMainLoop & GrCheckNextEvent - Code that worked fine (and still does)
: when linked against Pre2 (example below) ceases to function when linked
: against Pre4.


I'll take a look at this and debug it.  Thanks

Greg

: Between Pre2 and Pre4 have any modifications been made to the way
: GrMainLoop & GrCheckNextEvent - Code that worked fine (and still does)
: when linked against Pre2 (example below) ceases to function when linked
: against Pre4.
: 
: If the #if is set to 1 then the code functions partially then dies with
: a GrRead error.  I was just wondering if there was any changes that
: could effect the way my code is working....

I can't get the code to fail in nterm.c with the #if 1.

I do get a problem with #if 0 in nterm.c, but it can be
fixed with changing GrCheckNextEvent to GrGetNextEvent.
I will look into this.

Also, you might want to look at the client.c code for
GrMainLoop, and unroll it instead of using just GrCheckNextEvent.
Specifically, thats what GrPrepareSelect is for.

In any event, yes, there seems to be a bug with GrCheckNextEvent,
and I'll have to look into it.

Greg


: 
: Interesting enough, nterm.c gets the same problems (the read error) when
: compiled against Pre4, and that uses GrMainLoop, IIRC.
: 
: ----[ code snip ]----
: #if 0
:    GrMainLoop(HandleEvent);
: #else
:    while(1) {
:       GR_EVENT ev;
: 
: /* cycle_poll(main_loop)    */
:       GrCheckNextEvent(&ev);
:       HandleEvent(&ev);
:    }
: #endif
: ----[ end code snip ]----
: