Why EDID is not trustworthy for DPI
Robert Marcano
robert at marcanoonline.com
Tue Oct 4 19:07:33 UTC 2011
On 10/04/2011 01:24 PM, Adam Jackson wrote:
>
> I am clearly going to have to explain this one more time, forever.
> Let's see if I can't write it authoritatively once and simply answer
> with a URL from here out. (As always, use of the second person "you"
> herein is plural, not singular.)
....
Thanks for the explanation. This make me remember when everyone was
using CRT monitors. There wasn't a way to know from the hardware the
monitor refresh rates, so being careful, OSs defaulted to the lowest
setting. Why isn't possible to use the 96dpi hardcoded value and provide
an UI to that shows the hardware provided values? (or obtained using
those heuristics that sometimes fails), provide an UI action to try it
and revert if you do not like the results or 10 seconds without an
answer. At least trying a different DPI setting is not dangerous to the
hardware than trying a bigger refresh rate on old CRT monitors
More information about the devel
mailing list