> Here's two little patch files; can somebody who knows glut et > al better than me figure out of they are valid? I've done a > little test and it seems ok but...
One thing that occurs to me (from some further tests) is that if we take this patch (or even if we don't!) then it might be a Good Idea to put something in the docs to warn the end users not to mix'n'match using glutIdleFunc() with the Fl::[add|remove]_idle() methods, for the glut windows... With the patch in, the idea is that you can use FL::[add|remove]_idle() for your non-glut code and *either* glutIdleFunc() *or* Fl::[add|remove]_idle() for the glut windows - and the glutIdleFunc() *will not* break the other fltk idle functions (whereas the current implementation of glutIdleFunc() *does* break the fltk idle functions. As I discovered the hard way...) -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
