The breakLoop is somewhat like a Fl::flush . Removing a timeout should not really need it. Maybe using the flag as in may sample is "good enough"
On 03.12.2010, at 10:20, Manolo Gouy <[email protected]> wrote: >>> Actually, I am not entirely sure that we need to break the EventLoop >>> at all?! >>> >> Yes, this is a point I don't understand in all details either. But >> comment out this event loop break, run the threads demo, >> and increase the window size with your mouse. You'll be convinced >> this loop break is indeed useful. > > This first reply of mine is probably incorrect. Sorry for that. > > I have checked that the EventLoop break was not in file Fl_mac.cxx > (the Carbon version). Thus, I must have added it myself, but I confess > I don't remember why. I vaguely remember this was related to the > threads demo. But this demo runs and resizes well without this > statement. > > Removing this loop break would remove the interference with running > fluid in command mode (the tabs demo creates an Fl_Clock whose > destructor calls Fl::remove_timeout). But I don't feel safe to do > that without clarifying why this statement was introduced in the > first place. Any idea ? > _______________________________________________ > fltk-dev mailing list > [email protected] > http://lists.easysw.com/mailman/listinfo/fltk-dev _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
