-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
(Minor UI bug - Windows 10) Window width resizes after closing Settings>Options modal via "Close"/"OK"/"X" buttons #5886
Comments
I can't reproduce mentioned behaviour on my machine. can you provide your What is your screen resolution and font scale if you do use any? |
So looks like my To reiterate with more info, when I resize the dash window and then open & close SettingsModal, ONLY the WIDTH will reset back to original width, but the height does NOT reset. Some more tests:
What other info can I get you? |
that's strange, I guess it happens due to some certain minimal width that is supposed to be for Main window and which is reset after opening Settings window (even if no settings changed). hm... |
I can't recall when it started occurring either. I feel like it is relatively recent (as in last few releases?). I know there were some UI changes in the last number of months, right? So maybe the bug crept in during that time. Anyway, not a huge deal but it is annoying. So if it's easy to find/fix, hope it can be fixed in the next release! |
I have the issue on win11! Dash Core version v21.1.0 and even before this version had the same issue. I can confirm its just the width that resets, height stays at correct size! |
Expected behavior
Expected window width to NOT CHANGE when I close the Options modal
Actual behavior
When closing the settings window (even if no settings are changed, even if cancelling or clicking the X; did NOT test "Reset Options" button to see if it leads to the same effect.)
To reproduce
System information
Dash 20.0.4, from dash.org/downloads
Windows 10,
i7-8th gen,
SSD M.2
Windows 10 Home os build: 19045.4046
I want to say this bug appeared somewhat recently, in latest or or one of the latest versions. Low priority.
The text was updated successfully, but these errors were encountered: