-
Notifications
You must be signed in to change notification settings - Fork 108
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
Default window size on Windows 11 hides the " Start " button. #95
Comments
Strange question: Are you sure you are on Windows 11? I've heard about this problem, but only on Windows 10. |
I think this depends on the resolution/display and not so much on the OS. @kaixxx, do you remember that we had this issue on macOS as well. That's why we have different window sizes in macOS and windows. |
Yeah, you may be right. One easy solution would be to make noScribe fullscreen as a default. What do you think about that? It would only apply to the first startup. After that, the last window size is always restored from config.yml. |
We already have a min x (or better a completely default x). However, this seems to be rendered different on different machines. Might be a |
@Lod3 Thank you for investigating this further. A very strange behavior. This convinces me even more that I should make noScribe default to full-screen. If people have seen and used the start button at least once, they will probably recognize if it's disappearing later when they resize the window. The biggest problem right now is that some people might not be aware that the start button exists at all. Defining al larger default size in pixels is risky because you never know how this is interpreted on today's high-res screens (I have set my UI scaling to 200% in Windows on my 2880 x 1800 screen). |
When starting NoScribe the window dimension starts like this, hiding the blue "Start" button.
Non tech savvy users are going to be confused by this when following a guide for example and will think they did something wrong.
Currently the window needs to be reized downwards to reveal the "Start/Cancel" button.
The text was updated successfully, but these errors were encountered: