-
Notifications
You must be signed in to change notification settings - Fork 0
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] fixes initial placement, move and size issues #331
Comments
@redmunds do you mind taking a look when you have time? Thanks! |
Found a weird case:
Results: Then, if I Restore Brackets window size it switches back to secondary monitor! |
hmmmm...That is weird indeed. Not only that but it restores back to the secondary monitor which then maximizes back on the secondary monitor. |
I noticed another case:
Results: Expected Not sure if this is worth fixing. |
@redmunds regarding the issue you ran into with maximizing, disconnecting the monitor, restarting and clicking the restore button. In this case the Window is using CW_USEDEFAULT which lets Windows decide where to put the restored window. In some cases it's just using the minimum sizes which is 320x200. I could only reproduce this while running in the debugger so I rejiggered the logic so that we just don't set the restored window placement if it's off-screen which forces windows to just use CW_USEDEFAULT (which was passed in during initial window creation). |
@JeffryBooher This looks good on WIndows. Have you verified that this doesn't break Mac build? I upgraded my Mac to Yosemite and can't build Brackets at the moment. |
@redmunds this is only changing Windows project files -- it doesn't affect any cross platform code so I think we're safe on Mac. |
Merging. |
Friday Jan 09, 2015 at 23:13 GMT
Originally opened as adobe#498
FIxes the following issues:
JeffryBooher included the following code: https://github.com/adobe/brackets-shell/pull/498/commits
The text was updated successfully, but these errors were encountered: