Please keep us updated on your work with this. I had a similar problem
(trying to make sure I had the latest versions of stacks) although I
didn't go through the process of looking to see if the main stack was
open. I ended up downloading all the updated stacks (if necessary) and
then requiring the user to quit the application (after notifying them
that the software was updated). When they got back in, all the stacks
were updated and it started up.
I would much rather download what I need and then proceed to run the
program without the quit step.
Len Morgan
Shari wrote:
Epiphany!
Doesn't solve it, but explains it.
I think I know why the revert command causes the app not to launch.
The main app stack has this in its preOpenStack handler. So when this
script is running nothing is open yet. The objective is to create or
replace stacks if needed before anything else launches that will use
those stacks.
However, the pref stack has a caveat in it that if you attempt to
launch it and the main app is not open, it throws up an error and
everything quits. The objective was to prevent the opening of the
supplemental stacks if the main stack wasn't also open.
So when I tell it to revert, it must be loading the openStack handler
of the pref stack, seeing that the main stack isn't loaded, and quitting.
I have an idea for a workaround but must go elsewhere today. Darn it
all! I'd ruther be fixing this!
Shari
_______________________________________________
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
