Hey All, I have an FLTK 1.1.7 app that computes a very long function when the user presses a button. Since the function takes so long to compute, I use FL::check() within the function to update a progress bar. (Without this progress bar, it's pretty much impossible to tell whether or not the app is still running or just hanging.)
The problem is, FL::check allows FLTK to respond to additional events. So if the user tries to click the button again, the function will presumably start over. (I don't know how FLTK handles this--does it create a new thread? Does it just "cancel" what was happening before?) When the user clicks the button one or more times while the function is already running, I can get segmentation faults / assertion failures due to statements in the function, because the previous call did not properly terminate and clean things up. Ideally, I'd like the button to ignore subsequent clicks while the function is still being computed. Any ideas how I might accomplish this? Thanks, Tom _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
