bobsneidar at iotecdigital.com
Wed May 10 16:53:09 CEST 2017
I think what they do is launch an updater app just before quiting themselves. The updater stack replaces the app stack, launches the app stack then quits itself. Only way I would know how to do it.
> On May 10, 2017, at 04:35 , Graham Samuel via use-livecode <use-livecode at lists.runrev.com> wrote:
> I can kind of see how to do this (the splash stack checks with the server where the app originated to see if there is a more up to date version, then somehow replaces itself), but are there any gotchas in this approach? One I can think of so far is when the user runs the app offline, so that any approach to the server will fail - not sure how to detect that. Also, so far I am vague about how a running standalone can replace itself - something do do with file names, perhaps?
> I’d be grateful for any advice or experience.
More information about the use-livecode