-
Notifications
You must be signed in to change notification settings - Fork 75
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
Saving location? #57
Comments
One issue here, problem is if you are switching monitors, or number of monitors, Ruler will not be visible if it ends up off screen. |
@andrijac Should the app enumerate which monitor it is on and if the monitor is not there(when relaunched) fall back to the primary monitor(screen) at location on 3rd monitor? What are you meaning by switching monitors? The above is for a multiple monitor setup |
@IsaacMorris1980 switching monitors example: if you using laptop with docking station that is connected to 2 other monitors. There will be difference on and off docking station. We can implement this behavior but it should be optional. Also, I would separate option to save location and size. Location restore needs to check if it's visible on screen and size restore needs to check if it fits the screen. If not, fallback to defaults. |
Is it ok if i try this one ? |
@andrijac on my branch Saving Locaton i think i have this implemented(non-optional) . Now have to make it optional, but i dont have the multiple monitors to test that part with. |
Before Form is shown, in debugger, try setting the Location of Form outside your screen, giving it very large number for location. |
Will do, still working on making it optional, should have a PR soon |
Should have a PR soon not sure why when i only added a few items in pr it is like i am replacing it all. I am also adding screen check though i had it but on new branch i forgot to implement screen check. Sorry would have like to put a PR in today |
This is a great little program, but is it possible to save the location & size for future use?
The text was updated successfully, but these errors were encountered: