You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using v5.18.7.f, whenever I launch the app the window size is larger than last time and each column has grown in width. After a few launches, it gets to silly sizes. See #110 for an example screenshot.
Downgrading to v5.18.6.f fixes it, which makes me think it is related to the changes in #105, which were a fix for #103. I'm on Windows 11 and my scale is set to 125% (no custom scaling set) running at 2560x1440, with no custom DPI settings for transgui set in the Compatibility settings.
The text was updated successfully, but these errors were encountered:
Can confirm this is happening on Windows 10 where display scaling is set to 125%, resulting in the columns becoming so large that the program refuses to load/crashes as soon as you try to interact with it.
To fix it, open %localappdata%/Transmission Remote GUI/transgui.ini and edit any of the Width* values which have excessively large numbers. Mine had reached values in the hundreds of millions of pixels somehow.
Same issue for me using 125% DPI in Windows 10. Current workaround I've found is to set "High DPI scaling override" to "System" or "System (Enhanced)" within the "Change high DPI settings" button in the "Compatibility" tab of the executable's shortcut. While it seems to stop the growing width issues, it is not ideal as it makes the application blurrier/lower fidelity.
Using v5.18.7.f, whenever I launch the app the window size is larger than last time and each column has grown in width. After a few launches, it gets to silly sizes. See #110 for an example screenshot.
Downgrading to v5.18.6.f fixes it, which makes me think it is related to the changes in #105, which were a fix for #103. I'm on Windows 11 and my scale is set to 125% (no custom scaling set) running at 2560x1440, with no custom DPI settings for transgui set in the Compatibility settings.
The text was updated successfully, but these errors were encountered: