>>I have a situation where a client likes to set his shortcuts to run as maximized. However, we have an app that shows a top level form to login before _screen is shown. I can force the form to the right size but with the shortcut set to run as max, it flashes just before it resizes. How can I get control of a top level form in this scenario before the OS tries to maximize it?
>>(Btw, setting visible .F. in load() or anywhere else does not work.)
>
>You'd need to have a CONFIG.FPW with SCREEN=OFF compiled into your .EXE. That gives you full control of your code to set the size of things (non-visibly) before you actually "turn it on" (make visible).

SCREEN=OFF is set. That's not the problem. The problem is a top level form that is shown before the _screen object.

When the application object is created, a login form is launched in show(). A top level form to accept username and password.
Setting SCREEN=OFF doesn't apply to this form. Even setting visible = .F. in the form and setting the properties before showing it does not work with the shortcut set to run as maximized.

Interesting thing I just discovered though. If I turn off the titlebar on the login form, the OS maximizes _screen, not the login form. It's as if the shortcut maximizes the first window it can get it's hands on with a titlebar.