Summary: | provide designed viewing distance in addition to DPI | ||
---|---|---|---|
Product: | xorg | Reporter: | Stanislav Brabec <sbrabec> |
Component: | Server/General | Assignee: | Xorg Project Team <xorg-team> |
Status: | RESOLVED WONTFIX | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | enhancement | ||
Priority: | medium | CC: | horsley1953, mrmazda |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stanislav Brabec
2009-08-28 08:39:20 UTC
There is absolutely no effective difference between overriding the DPI and adding complicated angular diameter calculations to invent an effective DPI different than the physical DPI. Just give me an easy way to simply override the DPI on a per monitor basis and I'll be perfectly capable of making my displays readable regardless of whether I go through complicated trig calculations based on distance from the display, or I just change the number till it looks good :-). The problem is that all the ways you used to be able to override the DPI (like lying about the monitor size) are now being ignored by the X server which just knows it is smarter than you are. Providing false values for DPI, height and width to get required GUI dimensions seems to be an abuse, not the correct use, and it breaks expected API behavior. I can imagine many valid applications that depend on a true physical size. For example: "button just enough for a finger touch", "use the size of the physical (printed) template attached to the screen", "display millimeter gauge", etc. The angular calculation may be a purely virtual thing. That is why I propose a very obscure unit "millimeter as it is seen when placed in a standard viewing distance of a desktop display" and "dots per inch seen in a standard viewing distance of a desktop display". Porting applications to this extension would consist just from a several search/replace. These units are obscure but intuitive: If designed viewing distance of your display is equal to standard viewing distance, then DPIiaSVwD = DPI. If designed viewing distance of your display is two standard viewing distances of a desktop display, then DPIiaSVwD = DPI * 2. It will cause that physical sizes of fonts will be multiplied by two. DPIiaSVwD = DPI may be a smart default, if no value is provided. We don't have any way of knowing designed view distance; it's not something the hardware tells us. (In reply to comment #3) > We don't have any way of knowing designed view distance; it's not something the > hardware tells us. It needn't be provided by hardware. It simply needs to be an available user provided setting, as long as hardware cannot do it. It need not be "designed viewing distance" either. Simply "viewing distance" would be sufficient. (In reply to comment #4) > It needn't be provided by hardware. It simply needs to be an available user > provided setting, as long as hardware cannot do it. It need not be "designed > viewing distance" either. Simply "viewing distance" would be sufficient. That's something client conventions can handle. Not an xserver bug. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.