Open vchernin opened 3 years ago
This is likely an upstream wxWidgets bug.
Or is this a GTK issue? wxWidgets does not support GTK4; it is still on GTK3 and I doubt that will change for a long time. Do GTK3 applications usually adjust when switching to monitors with different scale factors?
Or is this a GTK issue? wxWidgets does not support GTK4; it is still on GTK3 and I doubt that will change for a long time. Do GTK3 applications usually adjust when switching to monitors with different scale factors?
GTK 3 also supports adjusting to monitors with different scale factors, I just tried it.
Guidelines
Version/Commit hash
https://github.com/flathub/flathub/pull/2444#issuecomment-907707785 (no commit hash with Flatpak apparently)
Describe the bug.
I have taken videos of what happens. Note the effect is exagerated here, since I usually have both monitors at 200% I had to create a weird setup and scale one to 100% to actually show the issue.
https://user-images.githubusercontent.com/38842733/131270478-076c1957-350b-40e1-94df-53eb7d8b482b.mp4
https://user-images.githubusercontent.com/38842733/131270482-038d6df2-28c0-4e23-b2f1-ed9c95f41f0f.mp4
Expected behavior
Tenacity adjuts to the scale factor of each monitor akin to GTK. That is what the user expects, and that is what most apps should do.
OS
Fedora 34 Wayland
Additional context
It seems Tenacity arbitrarily picks one monitor's scale factor to match. The only app off the top of my head which behaves similarly is Steam.
This issue is not a duplicate