> Ian: > > But in the context of a threaded app, a call to Fl::awake() will > > cause the fltk loop to do its thing. Since it is not possible to > > call Fl::flush() from a subsidiary thread, Fl::awake() is the best > > (and only, really) substitute.
> > Despite what the docs show, Fl::awake() with no args is a perfectly > > valid option. Indeed the original version of Fl::awake() had no > > args, they got added later. In this context (as a stand in for > > Fl::flush()...) they are not needed. Me: > Thank you Ian, I stand corrected. > I shall add your text to the docs. Done. See revision 6787 _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
