Has anyone found a workaround for the situation where a browser that was
launched from an MC stack is closed when MC is quit?
I've come to expect that "standard" behavior of MC's launch command is to
typically shut down any MC-launched app when MC is quit. However, I have
some clients who are able to successfully continue using their Web browsers
after they were launched by an MC stack that was quit. In fact, this is
very desirable behavior considering the fact that a user might go on to
compose their email or create a presentation, only to have their work
mysteriously lost when the MC application is quit.
Now I'm being asked to see if I can find a way to implement the above
behavior: allow a launched app to continue operation after my MC app is
quit. Might there be some way to achieve this?
Thanks for any ideas -- it's very difficult to explain to a client that we
can't implement a feature in our software which already occurs in our
software but shouldn't be there in the first place...
Regards,
Scott
_____________________________________________________________________
Scott Rossi Tactile Media - Multimedia & Design
Creative Director Email: [EMAIL PROTECTED]
Web: www.tactilemedia.com
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
