Hi Richard,
The info you provided doesn't make anything clear, because it says
nothing about how your scripts work. If I understand your original
post correctly, the problem is not the updating or downloading of the
stacks, but the inability to access the data. So, what triggers the
script that reads the data? Can you post the handler which calls this
script, for a start?
Mark
--
Economy-x-Talk
Consultancy and Software Engineering
http://economy-x-talk.com
http://www.salery.biz
Get your store on-line within minutes with Salery Web Store software.
Download at http://www.salery.biz
Op 11-okt-2006, om 14:33 heeft Richard Miller het volgende geschreven:
Hi Mark,
We actually have two programs that have similar updating processes.
Both of these are downloaded by our users from our web site.
This second program has three possible substacks, any one of which
may have an update waiting for download. We could have gone with an
automatic update process that occurs at startup, but the thought
was to give our users the option to update at their convenience.
With this second program, one of the substacks is a fair bit larger
and not something we necessarily wanted to force a user to wait for
upon startup. So an "update" button simply becomes visible on the
opening page of the main stack at startup if an update is available.
To answer your first questions, there's no preopenstack handler
involved and no lockmessages command used anywhere. The sequence of
commands is:
(From inside stack 2.. the .rev stack)
Close this stack
Open stack 1
(From inside stack 1.... the .exe stack)
Delete stack 2
Download new stack 2
Open stack 2
Thanks.
Richard
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
