replace “unlock screen” with “wait 0 seconds with messages”. The screen will
unlock when an idle message is sent, which is what will happen when you wait 0
seconds with messages.
Bob S
On Aug 27, 2014, at 04:34 , j...@souslelogo.com wrote:
> actually the loop is like this (my mistake) :
>
>
Björnke von Gierke wrote:
> while the screen is locked, in the repeat loop:
>
> wait 0 seconds with messages
>
> Annoying, and weird, I know. But it's been like that since a few
> versions now, so this "feature" probably will most likely stay
> like that.
Apparently it annoyed Mark Waddingham to
Thanks Björnke and Mark.
It does work now. I shall perhaps reconsider my old school
approach of several coding details like that one...
In the old days, locking the screen did speed up scripts that
needed lots of CPU times anyway...
jbv
___
use-liveco
Hi jbv,
Data processing doesn't slow down because of screen redraws. If a repeat
loop like yours needs a lot of CPU time, it will take this and less time
will be left for screen updates.
The lock screen and unlock screen commands themselves also take some
time. There's a good chance that a s
while the screen is locked, in the repeat loop:
wait 0 seconds with messages
Annoying, and weird, I know. But it's been like that since a few versions now,
so this "feature" probably will most likely stay like that.
On 27 Aug 2014, at 13:25, j...@souslelogo.com wrote:
> Hi list
>
> I have th
actually the loop is like this (my mistake) :
lock screen
repeat 2 times
-- do a lot of things
unlock screen
put myVar into fld "myVar"
lock screen
end repeat
but the problem remains.
jbv
___
use-livecode mailing list
use-li
Hi list
I have the following loop :
lock screen
repeat 2 times
-- do a lot of things
unlock screen
put myVar into fld myVar
lock screen
end repeat
The purpose is to lock the screen so that the heavy data
processing inside the loop isn't slowed down, but also to
display
