Full screen OS X client misbehavior in two screen setups

The OS X client misbehaves when dealing with two screens that are of dissimilar resolution. I have an iMac with normal screen, and an old VGA type Samsung monitor that is limited to 720 pixels. Problems observed:

1. If the launcher is brought up on the native screen - the normal case - the game will not always launch to the same screen. If the current mouse pointer position is on the 2nd screen, or the current top window with focus is on that screen (and probably some other conditions as well), the SotA will instead launch to the 2nd screen. A sideeffect of that is that graphics resolution is forced down to a 720 pixel mode, and this is saved by the app. Suggested fix: the game client should always launch to the screen where the launcher window is located.

2. If the app is then terminated, and relaunched successfully to the main screen, the resolution is now incorrect for that screen. While it takes over the whole screen, the actual imaging area is sub-screen, and IMPORTANTLY the UI targeting for the mouse is incorrect. The hot area for buttons, pull downs, etc. is displaced to the right of their visual area. This is frustrating as h***, and if someone doesn't figure out what's going on, a BLOCKER.

3. Additionally (and this has been going on since forever), the SotA app continues to track the mouse cursor when the mouse is on the second monitor, therefore outside SotA's active window, AND it also continues to do so when the SotA app does not have focus. (For instance, I see info popups for deco items that are off-screen in the SotA render when I move the mouse to the 2nd screen.) This is a violation of OS/X UI guidelines.

 

Have the launcher save the screen on which it's active to a game file, have the client initially launch faceless, then pick up the launcher info and bring up its window on that screen.