FLTK should destroy the X window representation (since the X window no longer exists), and call hide() to indicate to FLTK that the window cannot be seen.
It may also want to call close() so a program can exit cleanly. If the program does not exit, it can get the window back by calling show() (which will create a new X window). It can't destroy the FLTK window object, as the application certainly is not expecting that. On 05/16/2011 03:06 AM, Kurt Van Dijck wrote: > On Mon, May 16, 2011 at 11:00:05AM +0100, MacArthur, Ian (SELEX GALILEO, UK) > wrote: >> >>> almost. You should read: 'noone is using applications that do >>> XDestroyWindow' >> >> Um, my problem is that I'm not sure *other* apps are even permitted to >> call XDestroyWindow() on your app's window, > > see below > >> and from a fltk app, if we >> choose to close the window "internally" it all works OK. > ack. That scenario works perfect. >> >> So my concern is that handling calls of XDestroyWindow() from external >> sources - well, is that valid? I just don't know... > > Well, I'm not saying it's good practice. But luckily it is allowed. > X11 is very flexible... > > I'm not aware of how other toolkits respond to such. > > Kurt > _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
