DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2627 Version: 1.4-feature > If we do this, do we need to explicitly close the XIM context down > too (if it is in use)? I would say no, because the XIM context seems to be recreated each time the focussed window changes. See lines 886ff of Fl_x.cxx: if (fl_xim_ic && (xevent.type == FocusIn)) { #define POOR_XIM #ifdef POOR_XIM if (xim_win != xid) { xim_win = xid; XDestroyIC(fl_xim_ic); fl_xim_ic = NULL; fl_new_ic(); Thus, if the focussed window is externally destroyed, the focus will pass to a new window, and the old XIM context will be destroyed also. This should be properly tested though. > If we do accept the DestroyNotify event, do we need to consider > setting fl_destroynotified_xid back to NULL once we are done? I don't follow you. The patch reads: fl_destroynotified_xid = xid; window->hide(); fl_destroynotified_xid = NULL; so this variable is indeed set back to NULL after each use. Link: http://www.fltk.org/str.php?L2627 Version: 1.4-feature _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
