I see no reason not to put it in. For WIN32, it may be the WM_DISPLAYCHANGE message. It's sent for resolution changes, so it should be handled anyway.
For X11, I have no clue. Can it hot-plug screens? On 29.09.2011, at 19:07, Manolo Gouy wrote: > For Mac OS, do this: > - add this line to enum Fl_Event of FL/Enumerations.H > , FL_SCREEN_CONFIGURATION_CHANGED = 24 > - add this line at the end of function > applicationDidChangeScreenParameters in file src/Fl_cocoa.mm: > Fl::handle(FL_SCREEN_CONFIGURATION_CHANGED, NULL); > > and it does the trick. But I haven't found an API to receive > screen change events under MSWindows nor unix, so I let you decide > if it's appropriate to add this new FLTK event. > > >>> Author: manolo >>> Date: 2011-09-29 09:04:24 -0700 (Thu, 29 Sep 2011) >>> New Revision: 9084 >>> Log: >>> Fix STR#2695 & 2697: correct computation of work areas with multiple = >> screens. >> >> Great! Thank you. >> >> Do you think there is an easy way to add an event, say = >> "FL_SCREEN_CONFIGURATION_CHANGED", that will call all handlers = >> registered by Fl::add_handler() ? >> >> - Matthias >> > > _______________________________________________ > fltk-dev mailing list > [email protected] > http://lists.easysw.com/mailman/listinfo/fltk-dev _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
