fixes initial placement, move and size issues

[JeffryBooher]

FIxes the following issues:

• [CEF 2171] Droplists appear in wrong location brackets#10208
• Main Window shows up offscreen when Monitor is unplugged or screen size changes brackets#9742

[JeffryBooher]

calling this was something that needed to be added whenever the app is moved or resized

[JeffryBooher]

@redmunds do you mind taking a look when you have time? Thanks!

[redmunds]

Found a weird case:

1. Open Brackets in secondary monitor
2. Maximize Brackets, then shutdown
3. Restart Brackets

Results:
Brackets is opened in primary monitor. Note that I did not disconnect or move secondary monitor.

Then, if I Restore Brackets window size it switches back to secondary monitor!

[JeffryBooher]

hmmmm...That is weird indeed. Not only that but it restores back to the secondary monitor which then maximizes back on the secondary monitor.

[redmunds]

Verified that this case is now fixed.

I also notice that Brackets window is moved from secondary monitor if it's disconnected while Brackets is running! Sweet.

[redmunds]

I noticed another case:

1. Maximize Brackets on secondary monitor and close Brackets
2. Disconnect secondary monitor and restart Brackets
3. Brackets opens maximized in primary monitor as expected
4. Now click Restore button

Results:
Brackets window becomes really small (390x200). Brackets is unusable as an editor, but you can still grab edges, make window bigger, and then everything works as expected.

Expected
Would be nice if Brackets remembered my previous Restore size (obviously it needs to be re-_position_ed). If that can't be remembered, then maybe default size (1000x700) can be used.

Not sure if this is worth fixing.

[redmunds]

Can original width and height be maintained? i.e. only set left and top to default?

[JeffryBooher]

Well, this has to work for both the maximized size / placement and the restored size / placement otherwise you run into that odd case so, IMO, it's better to just let the OS decide initial placement and then let the user move it wherever they want.

This eliminates incorrectly computing the placement or placing the window on a secondary monitor (in the case they have more than 2 monitors and disconnect one or rearrange monitors.)

[JeffryBooher]

@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).

[redmunds]

@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.

[JeffryBooher]

@redmunds this is only changing Windows project files -- it doesn't affect any cross platform code so I think we're safe on Mac.

[redmunds]

Merging.