I think a lot of this was fixed in the fltk2.0 osx event handler. It calls a function called ReceiveNextEvent() which takes a timeout parameter, thus skipping the need to create any kind of timeout objects and working much more like the Linux and Windows versions. May be useful to back-port some of these fixes.
Note that we are doing extensive development on OSX here at The Foundry and thus the OSX version is quickly getting fixed up a lot. MacArthur, Ian (SELEX) (UK) wrote: >>> Without side-effects? >> No, so far I didn't notice any side effects. I don't really >> see why there >> would be any. Would you expect some? > > No - and it's good it works! > I just had a vague feeling that calling flush from the timeout might be > somehow recursive - but I can't think any good reason why that would be > so... > > Will you be posting an STR to flag this up "formally"? > > > > > 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
