> As far as I understand it, Fl::flush() and Fl::awake() have completely
> different purposes, so are probably not interchangeable. Fl::flush()
> deals with window redrawing, and Fl::awake() deals with threading.

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.


> What I also notice is that your Fl::awake() call is missing 
> an argument.

Despite what the docs show, Fl::awake() with no args is a perfectly
valid option. Indeed the original version of Fl::awake() had no rags,
they got added later. In this context (as a stand in for Fl::flush()...)
they are not needed.



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

Reply via email to