Hi Alex,
This is fairly long but there is no code in the explanation. I ran into this
problem last year. I have a stack that monitors 3 security systems. You can
switch between the system with the one stack or you can use 3 separate stacks
to monitor the different systems.
Here was my
Yeah, that seems like it might work - but it doesn't.
on mouseUp
put 1 && the lockscreen after msg
set the lockscreen to true
put 2 && the lockscreen after msg
wait 0 seconds with messages
put 3 && the lockscreen after msg
end mouseup
gives
1 false
2 true
3 true
I
There IS a method for unlocking all. wait 0 seconds with messages. All screen
locks are cleared when the idle message is sent.
Bob S
> On Dec 31, 2018, at 07:00 , Alex Tweedly via use-livecode
> wrote:
>
> So it needs to work like a nested counter - but maybe there should be a
>
On 31/12/2018 13:33, Sannyasin Brahmanathaswami via use-livecode wrote:
Aloha Malte:
I agree with this. I can't imagine any use case where the last attempt the message path/hierarchy,
to unlock screen, would where you actually *want* to have the screen locked. This has been a
"nuisance" for
Aloha Malte:
I agree with this. I can't imagine any use case where the last attempt the
message path/hierarchy, to unlock screen, would where you actually *want* to
have the screen locked. This has been a "nuisance" for years. As you say, it is
a property, on/off, and should not be
Aloha Malte:
I agree with this. I can't imagine any use case where the last attempt the
message path/hierarchy, to unlock screen, would where you actually *want* to
have the screen locked. This has been a "nuisance" for years. As you say, it is
a property, on/off, and should not be dependent
