I've got a stack that tests to see if QuickTime is installed at the
start. If QT is not installed, it offers to run the standard QT
installer.
I'm using qtVersion() to check whether QT is installed and which
version is available. However, having run the QT installer, when I
use qtVersion() again (to check that the user did actually do the
installation and didn't abort it), I still get "0.0" indicating that
QT is still not installed. My stack then quits as it thinks QT isn't
available. Yet if I immediately re-run my stack, it senses the new
QT installation and proceeds happily.
Is there any way I can "refresh" the qtInstalled state within my
stack so I can test whether it's safe to proceed since QT has been
installed?
If not, then I'll need to run the QT installer and quit my stack
having prompted the user to re-run the stack after the QT
installation is complete. I'm not sure that I can sensibly get my
stack to run itself again??
This begs the next question - can I "launch" an application (e.g. the
QT installer) and immediately quit my stack? This doesn't seem to
work - the launch works OK, but the launched app is then terminated
as soon as the launching stack quits! It seems I have to await the
end of the launched app using something like:
wait until lauchedApp is not in the openProcesses
only then can I quit my stack.
Any suggestions please, this is a last minute hiccup that's delaying
the pressing of a CD!
Thanks
Peter
--
--------------------------------------------------------
Peter Reid
Reid-IT Limited, Loughborough, Leics., UK
Tel: +44 (0)1509 268843 Fax: +44 (0)870 052 7576
E-mail: [EMAIL PROTECTED]
Web: http://www.reidit.co.uk
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.