0
From: "J. Landman Gay" mailto:jac...@hyperactivesw.com>>
To: How to use LiveCode mailto:use-livecode@lists.runrev.com>>
Subject: Re: Device implementation problems
Message-ID: mailto:d0ef401f-b0c1-93a9-85a1-6058181fb...@hyperactivesw.com>>
Content-Type: text/plain; chars
That is true. However, just adding the single command "lock screen" before the
"go card xyz" removes the problem. I have tried to understand what could be
"illegal" in the target device point of view in the script code following, but
so far haven't figured it out. Actually the script runs unt
On 11/3/17 12:55 AM, Pyyhtiä Christer via use-livecode wrote:
When I issue the "go" and let the script run, many of the objects won't get done completely, for example card
background, button or field colouring gets only partially done. However, if I either add "lock screen" before the
"go" sta
I've seen this happen when something goes wrong in the code and in a standalone
that can fail silently. If it does, the engine exits to top and that is why
things get left undone.
Bob S
> On Nov 2, 2017, at 22:55 , Pyyhtiä Christer via use-livecode
> wrote:
>
> A few days ago I raised the
A few days ago I raised the question on how the device behaviour differs from
how it is in the IDE environment. The question posed was if there is a command
go card "xyz"
and the script continues to run immediately, would there be interference in
terms of "getting the go done".
Interp
