© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #16)
> See http://
Some comments:
> <ohsix> not a lot of people are bothered, since getting the per display dpi
> right is a hard problem, even if you can set it for one single monitor in
> particular, 'fixed' is handling some difference in dpi across displays,
> which doesn't happen in the toolkits or anything
Wrong. *I* am bothered, and *I* operate a few dual-monitor setup including those with different display DPI. That ohsix windows migrant would have a hard time telling me that forcing DPI to a semi-arbitrary value to follow the obsolete windows suit is right (and that it is worth breaking what used to work since last century).
> <ohsix> maybe you misunderstood me, i was telling you what's expected to do it
By whom? Those who smoked windows crack and a gazillion of tray notifiers?
Thanks but no thanks. I've seen enough weird video hardware (e.g. Acer V550 monitors reported those funny EDID values) but those are rather *exceptions* to be handled, and one can even automate that -- if a display has DPI less than e.g. 30 or higher than e.g. 300 (as of today) then it might be treated as a reason to fall back to default (96 is ok here) since those who operate special cases *can* be expected to know their ways around hi-res displays or display walls.
> <ohsix> any cobbled together thing where nobody really cares
> is going to miss details like that
This bastard should not continue to erode free software. *He* doesn't care.
Seems that Red Hat has hired too many dumb morons who took their windows habits and attitude there, see also http://
PS: just in case, I'm using and developing free software since 1998 and have done numerous migrations for people and companies. I know that care *is* crucial. Good luck to Xorg team with preserving that.