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 First of all we don't "need" Fl::x(),,,Fl::w() any more if we have the method to get each screen's working area as suggested by Ian. We could deprecate it then. If we did this, then the only question is that of compatibility with software that is using it. I'd say that these methods /should/ return the work area dimensions of the first/main monitor to be mostly consistent. On Windows this would be fully compatible with all previous versions. I think that X w/o Xinerama gives us only one display area, even with a multi-headed display, as Ian wrote. Maybe only in this case we would return this working area's bounds, and this would be a platform-dependent exception that could be documented. X with Xinerama would then return the first screen's working area. I don't know much about OS X though, but if it doesn't break things, I'd prefer consistency, so that it should always return the work area of the primary (not the focus-containing) screen. For all other cases, users should use the new methods that let them get the correct values of on specific monitor. 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
