Skip to content

Window and columns get larger on each launch #118

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
StormPooper opened this issue Dec 7, 2024 · 7 comments · Fixed by #127
Closed

Window and columns get larger on each launch #118

StormPooper opened this issue Dec 7, 2024 · 7 comments · Fixed by #127
Assignees
Labels
bug Something isn't working
Milestone

Comments

@StormPooper
Copy link

StormPooper commented Dec 7, 2024

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.

@stom66
Copy link

stom66 commented Jan 18, 2025

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.

@natediz
Copy link

natediz commented Jan 19, 2025

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.

@lighterowl lighterowl added the bug Something isn't working label Jan 24, 2025
@lighterowl
Copy link
Owner

Thanks. I always use a new ini file when testing so no wonder I haven't noticed this. My daily desktop is 100%.

@lighterowl
Copy link
Owner

Please try out the build available at https://github.com/lighterowl/transgui/actions/runs/12995815756 and let me know if this is still happening.

@StormPooper
Copy link
Author

Please try out the build available at https://github.com/lighterowl/transgui/actions/runs/12995815756 and let me know if this is still happening.

Thanks @lighterowl, just finished testing it now. On the first launch with this version, the window size and column sizes still grew as per the issue, but upon relaunching they stayed the same size. I was then able to adjust them back (I had to resize the window after the columns to remove the horizontal scrollbar) and now when I relaunch they don't grow.

@lighterowl
Copy link
Owner

lighterowl commented Jan 29, 2025

On the first launch with this version, the window size and column sizes still grew as per the issue

That's expected because the already-badly-resized widths were saved to the .ini the previous time transgui was shut down, which was the version without the fix.

Glad to hear it's working as expected now, thanks for testing.

@StormPooper
Copy link
Author

That's expected because the already-badly-resized widths were saved to the .ini the previous time transgui was shut down, which was the version without the fix.

Figured this would be the case but thought I'd mention it.

Glad to hear it's working as expected now, thanks for testing.

Thank you for sorting it so quickly, much appreciated, and again for your continued work on the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants