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. > It's a shame that outside of larger DEs like GNOME where this is all > integrated, X11 and widget libraries just fall apart. I'm not sure what the > best solution is to address this, but something needs to be done since it's > dire. Well, X11 was supposed to use x resources and it mostly does. But applications like XV (and FvwmScript) insist on laying out windows by pixel. So some applications may be X11 based but still have issues. Can you tell I'm not an FvwmScript fan? A few years ago I spent a couple of days trying to make FvwmForm and FvwmScript use shared code to create their widgets. Unfortunately, the French comments in FvwmScript defeated my attempts to understand what goes on in FvwmScript. In my opinion, FvwmForm does all it's layout correctly, working off the fonts it's using. Plus it has a GUI to configure the fonts it uses so you don't have to mess with a config file. So, since you dropped FvwmForm in fvwm3 did you add an FvwmScript dialog to configure FvwmAnimate? -- Dan Espen
