DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2697 Version: 1.3-current I propose the attached screens.patch to fix this STR as well as STR#2695. It introduces 3 new API functions static void Fl::work_area_xywh(X,Y,W,H); static void Fl::work_area_xywh(X,Y,W,H,mx,my); static void Fl::work_area_xywh(X,Y,W,H,n); that compute the bounding box of the work area of a screen (with cursor, at given point, of given rank). Functions Fl::x(),y(),w(),and h() now return values for the work area of the main screen, and are not used anymore by menus. On Mac OS, a callback is called at application start and whenever screens are changed, thus FLTK applications can be aware of screen changes without restarting (see STR#2600). On X11, I did not find an API to get the work area of a single screen, thus Fl::work_area_xywh() gives the same as Fl::screen_xywh(). The Fl::x()... functions do return a work area, but for a global object that encompasses all screens. For these functions to be consistent across OSes, it would require to change them on X11 and have them return the same as Fl::screen_xywh() for screen 0. I didn't do that yet. I believe to have tested all that well with multiheaded systems on Mac OS X, MSWindows and Linux/X11. Could any other developer try it also? Link: http://www.fltk.org/str.php?L2697 Version: 1.3-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
