On 5/12/17 4:20 AM, Graham Samuel via use-livecode wrote:
your method also avoids the issue of launching a completely automatic
update without giving the user an opportunity to refuse. So you just
get the user to run the installer, the same way as Tiemo does - is
that right?
It would be if I
An: How to use LiveCode <use-livecode@lists.runrev.com>
Cc: Graham Samuel <livf...@mac.com>
Betreff: Re: Update strategy?
Thanks again Jacque
Yes, I see the wisdom of that - your method also avoids the issue of launching
a completely automatic update without giving the user an opportuni
det: Mittwoch, 10. Mai 2017 20:00
An: How to use LiveCode <use-livecode@lists.runrev.com>
Cc: Graham Samuel <livf...@mac.com>
Betreff: Re: Update strategy?
Yes, but what if you want to update the launcher itself? Maybe I have made my
‘splash’ stack too rich in function, but I ca
On 5/10/17 1:00 PM, Graham Samuel via use-livecode wrote:
Yes, but what if you want to update the launcher itself? Maybe I have
made my ‘splash’ stack too rich in function, but I can easily see it
needing revision. Because of this, I’m thinking of altering the
structure of the app so that the
Yes, but what if you want to update the launcher itself? Maybe I have made my
‘splash’ stack too rich in function, but I can easily see it needing revision.
Because of this, I’m thinking of altering the structure of the app so that the
update code is more or less all that is in the standalone
On 5/10/17 8:10 AM, Graham Samuel via use-livecode wrote:
I have already got the idea of the text file and the test you
mention. I now have to experiment with the “open invisible” approach.
I have had so many problems with the IDE when trying to open two
stacks with the same name (it’s
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.
Bob S
> On May 10, 2017, at 04:35 , Graham Samuel via use-livecode
>
Your conflicting name problems is an example of why it is often best to
have an "updater" or "installer" stack or executable.
What gets downloaded and run is a stack whose function is to shut down
the old stack and clear it out of memory and download the new version
and set it up and then exit
m Samuel via use-livecode
> Gesendet: Mittwoch, 10. Mai 2017 13:35
> An: How to use LiveCode <use-livecode@lists.runrev.com>
> Cc: Graham Samuel <livf...@mac.com>
> Betreff: Update strategy?
>
> Apologies if this has come up relatively recently, but I have not been ver
use-livecode@lists.runrev.com>
Cc: Graham Samuel <livf...@mac.com>
Betreff: Update strategy?
Apologies if this has come up relatively recently, but I have not been very
attentive to the list for a bit…
I have a desktop app (though in principle it could be on mobile) which use
Thanks for the quick reply, Paul!
I have already got the idea of the text file and the test you mention. I now
have to experiment with the “open invisible” approach. I have had so many
problems with the IDE when trying to open two stacks with the same name (it’s
impossible AFAIKR - because LC
There are a number of ways to potentially do this, but you have the gist
already.
I'd recommend a check for updates that just fetches a text file with the
latest version number from your sever with a : Put URL into tSomeVar
check the result for any error, such as the internet not being available
Apologies if this has come up relatively recently, but I have not been very
attentive to the list for a bit…
I have a desktop app (though in principle it could be on mobile) which uses a
variant of the ‘splashscreen’ structure. What happens is that the app as seen
by the operating system is
13 matches
Mail list logo
