MacArthur, Ian (SELEX GALILEO, UK) wrote: > ... > Is that the kind of thing you were suggesting? I guess that does the > right sort of thing - we can have one idle function associated with the > glut window, and it can be enabled/disabled without breaking any other > Fltk idle functions we may have added. > > But... is "current_glut_idle" static, so it applies to all glut windows > in an app, or do we have a separate "current_glut_idle" value for each > glut window...? And if so, how does glutIdleFunc() find the right > instance? And... I really have no idea... I guess that "traditionally" > there would maybe only be one glut window, and therefore only one glut > idle function?
I'd make the idle function a non-static member of the class. That way each GLUT window can have its own idle function, and the default window will provide compatibility with existing apps. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
