> This is a long thread, so I may have missed it, but what > mechanism is being used to break out of the FLTK Fl::run() loop? > > Normally some external event like either > mouse/keyboard/window event > is needed to break out of the run() loop, or via an FLTK timer, > or Fl::add_fd() [which only works on unix].
IIRC, the OP was using some means to poll a shared memory buffer, and that poll was trigerring the updates. The actual mechanism underlying this I'm afraid I don't know - but I guess there might be something there that accounts for the aberrant behaviou on win32... 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
