> time have it use Fl::first_window() and Fl::next_window(...) in a loop > to find and each window the app has open, and then hide() each of these > in turn. > Again, I think this will do what you want. > > Any good? > > Thanks, thats great, i am set from there, i am also glad that my design structure was not called into question too much haha, maybe i'm not too far off the mark there now then...wait..dont answer that haha. Yes i saw a method in another FLTK tutorial a while back similar to the first 'hack' one you mentioned, i think the tutorial author was quoting it from a Greg E example or somebody else from here at the time.
I thin i prefer the second example, simply as it uses FLTK calls and i don't really like globals other than const vars where possible. Regarding hide() so if this is called i can in effect consider it deleted? the memory will not be freed until the program completely exits though? and so show () can be called to see same instance of object again.. why does a window get deleted if hidden but not if showing when mainwindow is destroyed behind it as in my example? Hide is totally fit for purpose considering during runtime the user may well wish to use the helper windows again, and good for my input error windows too. too. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
