MacArthur, Ian (SELEX GALILEO, UK) wrote: >>> 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. > > > Yes, I think that sounds like the most useful option, so if you had > multiple glut windows within your fltk app, each could have it's own > unique idle function. > > But what I'm not getting (and I hope I'm just being stupid here) is how > glutIdleFunc() is meant to determine the correct glut window?
IIRC, there is a "current" window in GLUT that we can use. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
