DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2774 Version: 1.3-feature True - but note that this is (more or less) by design, it is not a mistake or oversight as such. Note that the fltk docs explicitly advise against accessing the (Xlib, in this case) layer from multiple threads - all the GUI access should be in the main() thread, with only access via fltk's own methods (and using fltk's own locks) from any subsidiary threads. I recognise that this may not sit well with everybody's use-case, but in our experience this has proven to be more robust and portable (and faster) than depending on the (various, different) way Xlib (and other GUI systems) implement this functionality. Link: http://www.fltk.org/str.php?L2774 Version: 1.3-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
