On 07.01.2011, at 11:13, Manolo Gouy wrote:

>> 
>> On 07.01.2011, at 02:33, [email protected] wrote:
>> 
>>> Author: matt
>>> Date: 2011-01-06 17:33:29 -0800 (Thu, 06 Jan 2011)
>>> New Revision: 8206
>>> Log:
>>> DPI fixed for Xinerama?
>> 
> 
> 
> About Fl::screen_dpi() on Mac OS:
> 
> unfortunately, the system function userSpaceScaleFactor
> always returns 1 (unless special measures are taken, see below)
> whatever the screen and screen resolution you use. I have here
> a MacBook Pro and an external display. If I change the resolution
> of any of them, Fl::screen_dpi() always returns the same 72x72 ppi
> even though the real size of windows much changes.
> 
> See
> http://developer.apple.com/library/mac/#documentation/UserExperience/Conceptual/HiDPIOverview/HiDPIConcepts/HiDPIConcepts.html
> and specially its "How to Change the Scale Factor" part
> that explains that the userSpaceScaleFactor call is close to useless.
> 
> There's another issue with userSpaceScaleFactor in that it requires
> Mac OS X 10.4

OK, well, I did this to do the Dillo developers a favor. Now, since pretty much 
all the OSs lie (which shouldn't come as a surprise, because until HDMI the 
data exchange between screens and graphics cards has been very minimalistic), 
we should probably not go beyond what's in FLTK2. Dillo has been living with 
this false data from the OS, and their developers must have figured out a way 
to deal with it. At least we have an API in FLTK now.

As for OS X 10.3, I could try run-time linking?

 - Matthias

_______________________________________________
fltk-dev mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-dev

Reply via email to