[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #49627] Incompatible "screenpixelsperinch" pro
From: |
Hartmut |
Subject: |
[Octave-bug-tracker] [bug #49627] Incompatible "screenpixelsperinch" property |
Date: |
Wed, 16 Nov 2016 21:55:14 +0000 (UTC) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:49.0) Gecko/20100101 Firefox/49.0 |
Follow-up Comment #1, bug #49627 (project octave):
(also copied over from bug #45600:)
I have just realized (see bug #49612, comment #2) that also the "plain"
pixelnumbers (wd and ht in commment #12 of bug #45600) will be "un-real" on
modern Windows systems. The factor between the real physical pixel number, and
the pixel number given by VERTZRES and HORZRES seems to get scaled by Windows
via the High-DPI setting (a scaling of 200% in the case of bug #49612 under
Win10). Only on my very old WinXP machine the wd and ht values are returned
correctly.
In this light, I think the Matlab decision is not so bad (for Windows): to go
for a fixed "dpi" resolution of 96, and let the user decide (via his Windows
high-dpi setting / scaling) how "big" he wants to have his pixels.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?49627>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Octave-bug-tracker] [bug #49627] Incompatible "screenpixelsperinch" property,
Hartmut <=