On 5 Mar 2008, at 18:47, Alvin wrote: > 1. Using Fl::grab() on a hidden window. At the start of the > calculation, "grab" the window which, if I read the docs right, would > prevent the user events. Upon completion, I would ungrab the window.
How well grab works depends heavily on what OS, Xserver, WM, etc., you have, so probably is not a robust solution... > 2. Using some kind of semaphore/lock method. Basically, I set a > "busygoaway" > flag to true. Then, in the slider's callback, if "busygoaway" is > set, do > not allow the slider to be changed. This may work, but what if the > input > file is closed by the user during the calculation. I guess I would > need to > check the "busygoaway" flag in every possible operation?? Sounds like it could work. > 3. ???? Dunno... what's the actual nature of the segfault? Maybe there's something there that could be "fixed" so that the user could interact (and be ignored?) without triggering a fault? _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
