Well no luck with RUN and a line number. That won't nmake it active, either. Now SHELL will make active the opening app, but I'd say reliability would be out the window with repeated shell and system calls, any we'd need a file system to inform the new app what to print back to the screen and where in the code to go. PITA even if by some Christmas miracle you could get it to reliably function.
_FULLSCREEN with _FULLSCREEN _OFF won't stop the previous app window from being displayed in front of the full screen app. Oh, and of course _SCREENICON won't un-minimize just because we pop a _FULLSCREEN command after it.
Well on to other things. I'll check back later to see if someone found a trick or routine I don't think of.
Pete
_FULLSCREEN with _FULLSCREEN _OFF won't stop the previous app window from being displayed in front of the full screen app. Oh, and of course _SCREENICON won't un-minimize just because we pop a _FULLSCREEN command after it.
Well on to other things. I'll check back later to see if someone found a trick or routine I don't think of.
Pete