DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2159 Version: 1.3-current I posted a new diff file [1] for fltk 1.3-r6668, because your included patch didn't work for me without manual action. I can confirm what you see: fl_alert() windows popping up, but only one stays. This is a known problem (new fl_message() et al. windows "stealing" the previous message window). What exactly happens, if you close the window with the close button? I can see that the window is closed, but the application doesn't terminate. It uses 100% cpu on my system. Is this the same for you? ----- Fix #1: The diff file [2] fixes this problem only, i.e. the application terminates correctly when closing the window. The problem was that there were as many nested event loops (fl_ask.cxx / innards() / Fl::readqueue()-loops) as "stolen" message boxes. After dragging for a longer time, this will crash the application (stack overflow or memory problem). I don't have a fix for the primary problem that "dragging ignores modal()" yet :-( Please verify fix #1. ----- [1] http://www.fltk.org/strfiles/2159/valuators.fl.diff [2] http://www.fltk.org/strfiles/2159/slider_fix_v1.diff Link: http://www.fltk.org/str.php?L2159 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
