Dan Espen <dan1es...@gmail.com> writes: > Thomas Adam <tho...@fvwm.org> writes: > >> On Wed, Aug 12, 2020 at 06:54:53PM -0400, Dan Espen wrote: >>> Recently I went from a 1600x1200 monitor to a 3840x2160 monitor. >>> >>> Fvwm was the least of my problems. >> >> Same here. Mind you, even on laptops with 4K screens (so-called HiDPI), the >> situation is diabolical. X11 really doesn't work seamlessly in these >> conditions. I've resorted to all sorts of xrandr --dpi tricks without much >> success. >> >> Even if you do manage to get some scaling working, you're still left with the >> various widget libraries playing nicely with different applications. For >> example, on this laptop which has: >> >> % xdpyinfo | grep dimensions >> dimensions: 3840x2160 pixels (1016x571 millimeters) >> >> Firefox looks fine now that I've wrangled everything, but menus, buttons and >> other widgets are so small I can't even see what I'm clicking on half the >> time. Messing with GDK_SCALE env var and others helps, but it's still not >> great. > > Hmm, I got the Firefox menus under control but I'm going to have to dig > to find out what I did. I remember struggling with it for a while.
Found my notes on Firefox (copy pasted from somewhere): Firefox implements a similar sort of pixel scaling, but it doesn't seem to figure out when to use it on its own. The solution is to go into about:config and set the layout.css.devPixelsPerPx knob to a value like two. -- Dan Espen