Technically, yes, you can launch B and quit A. In fact, I believe the Flex SDK
Installer does that. I think NativeProcess will do the launch. You may have
to deal with path issues but if you get the path right, it should launch. And
then I think it is NativeApplication that will quit the app.
HTH,
-Alex
On 6/15/20, 9:37 AM, "Paul Stearns" <pa...@compuace.com.INVALID> wrote:
Is there a way of stopping execution of application "A" and transferring
control to application "B" in AIR?
Or will I need to create an OS command procedure?
My thought is to write an application whose only purpose is to verify that
my "real" application is up to date, download any SWF files which are out of
date, and then start the real application.It appears I can create an
"Application Domain" and load things into it, but for my purposes, if I could
stop execution of one application and start execution of a second, that would
be best.
If this can be done in AIR, rather than OS command procedures, then I won't
need to deal with Command procedures for Windows, Mac & Linux.
Paul R. Stearns
Advanced Consulting Enterprises, Inc.
15280 NW 79th Ct.
Suite 250
Miami Lakes, Fl 33016
Voice: (305)623-0360 x107
Fax: (305)623-4588
