Tijl Coosemans wrote: > On Saturday 12 April 2008 05:11:30 James McKenzie wrote: > > > Tijl Coosemans wrote: > > > > > Maybe a dumb question, but why is this setting in winecfg in the > > > first place? Why can't Wine simply use the DPI info from the X > > > server? > > > > > > > Simple, the DPI setting may be incorrect. I've seen folks using > > small fonts (96 dpi) on screens with 1024x768 or higher resolutions. > > This would make some programs open into too small an area to be > > usable. Add to this that winecfg does emulate the ability of some > > systems to custom set the dpi value (I use 133 on my Thinkpad and 120 > > on my Mac because of the screen layouts, as I've stated in this > > mailing list before.) Thus this ability was retained and a default > > of 96 dpi was retained. > > > > You can set the DPI of your monitor using DisplaySize in the xorg.conf > Monitor section. I don't understand why Wine needs to be different from > other X apps when it comes to this. DPI is a server side setting, not > client side. Really, the only good reason I can think of is that, due > to bad API design and/or sloppy programmers, there may be Windows apps > which GUI doesn't scale properly on higher DPI monitors. For instance, > when font sizes are set in points while some GUI elements are measured > or positioned using pixels. You are correct. From my experience with windows over number of years if you try to set DPI to anything other then standard 96 - expect some programs do look bad/break completely. And if DPI set to something other then 96 or 120 - things break for lots of apps (not 1-2).
