Hmmmm ... I could be wrong (Haven't done it myself), but I thought the
usual way to do this was to have a "splash screen" approach
- the splash screen stack starts up and quickly displays a splash screen
- then it checks for a new version.
and if there is one the splash stack downloads the new "real"
stack
- then the splash stack replaces the old "real" stack with the new
"real" stack
- then the splash stack transfers control to the "real": stack
(with many variations about when / where / what you ask the user ....)
but the essence is that the downloading / replacing is done by the
splash stack, not by the real stack, so there is never any need to
replace the stack file which is running.
-- Alex.
On 29/04/2012 18:57, Peter Haworth wrote:
Got everything working nicely with my handler to check for a more recent
version of my program. The final step after downloading is to copy the new
version of the program to wherever it needs to go on the user's computer
but I can't do that because the program is running (this is on OS X but I
assume it would be the same on other OS's).
I'm guessing the way to do this is instruct the user to quit the program
,have a handler that fires when the program closes that knows a new version
is ready to install and launches an Applescript (on OS X) to do the copy
and start the program again. Am I on the right track?
Pete
lcSQL Software<http://www.lcsql.com>
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
