Recently, Blair mail wrote:
> The only odd thing is that when you close the MC launcher app it also closes
> the browser with it. Strange. Ideally, you would want the MC launcher app to
> disappear on launch and leave the browser up as an independent entity. Any
> idea of a workaround for this?
If your software/delivery package can accommodate an extra 1.3MB or so,
there is indeed a workaround. The concept is to create a standalone
launcher app which handles your launching and then shuts down. The launch
process looks something like this:
Your App --> Launcher App --> Browser (or other application)
Using this technique it is possible to decouple the launched application
from your stack.
This behavior has bugged me ever since I started MC to launch external
applications. Thanks to list member JBV (sorry, I don't know this person's
name) I've built out a workaround over the last few weeks that seems to be
flexible and reliable. This also handles a number of "real world" problems
that occur when faced with browsers other than IE and NC. The only drawback
is the additional 1+ MB file required, which can be a lot in the case of
downloadable stacks/apps.
I'll try to get this posted in the next few days.
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.
