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
MassCode Window not on the only screen when disconnected from multi monitor setup #401
Comments
Same here when using masscode with Windows 10 Pro. |
I have this issue as well on Windows 10 Pro. As long as the massCode application is on the primary window when you close the application or open and running when you change the number of monitors you are using then the application will stay on the main window. However if it is closed on a window that is not your primary window and then the number of monitors changes then the application doesn't have a way to check that and so it opens on a monitor that is no longer available. I believe this can be handled in a function inside the CreateWindow() function under src > main > index.ts so that when you load the bounds of the application it then checks to see if those bounds are still within the current available displays. If true then it continues creating the window otherwise it will reset the window to be on the primary monitor. I think the call is pretty simple. It just needs to check the app bounds against the election screen.GetAllDisplays() result. I have done something similar in another application and am currently working on applying that solution to this app. |
this is not a masscode issue in itself, its an windows issue. what should work is select icon, hold windows key, use arrowkeys left several times to bring it to the main window permanent toolless workround, if you dont use your laptopscreen while bigscreen is connected rearrange it in display settings. move it to the right. |
Describe the bug
When opening the masscode window, it is hidden out of the desktop.
To reproduce
Version
3.7.0
OS
Win 11
Validations
The text was updated successfully, but these errors were encountered: