On Sep 20, 2007, at 8:12 PM, Stan wrote: > Thanks Matt, but I was asking a slightly different question. > I'm trying to find out if it's possible that by the time my > app is executing the callback code the window has already been > deleted (by fltk). If it was the last visible window, for > instance. I think the answer is "no, that's not > possible" (in fact, I think I've just about figured out what > my problem really is, and it's elsewhere); this is just sort > of a sanity check.
That's what I meant to answer. It is just a regular callback, no special processing was done at that point, meaing, if the callback gets called, the widget still exists. The callback does not get called as part of the hiding or deletion process. It is a reaction to the user pressing ESC or clicking the [x] button. It is then up to you if you want to hide or delete the window. If you don't, pressing the [x] will not close the window or end the application (which may be surprising for the user). So the order is: -> user interaction -> callback -> hide (or whatever other action) Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
