On Wed, Nov 1, 2017 at 9:35 PM, Adam Jackson <a...@nwnk.net> wrote: > On Wed, 2017-11-01 at 21:04 +0100, Giuseppe Bilotta wrote: > >> (Heck, I would even argue that the core DPI should be set to the >> primary monitor DPI by default, regardless of whether the system has >> one or more than one monitor.)
> The primary monitor can change at runtime. The core DPI is only sent at > initial connection. What would you like to do? Don't clients get an RRScreenChangeNotify already when the root window size changes? > Also: what's stopping us from fixing libXft instead? The core DPI as fallback of Xft.dpi is something that most toolkits follow as a rule, it's not just a libXft thing. It also makes perfect sense for single-monitor setups, since it reduces the pain needed to ensure proper UI scaling when switching resolution. AFAIK GTK3 is the only toolkit that stopped doing it, and to me that actually counts as a regression, as it makes it much harder to change the scaling of GTK3 applications when I change my output resolution (e.g. when I switch to projection mode for a lesson, and then back to using only my built-in laptop for work). I would rather not have libXft broken this way as well. -- Giuseppe "Oblomov" Bilotta _______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
