Hi Bob,
I'm not sure from your description how / when you are seeing the
(unexpected) changes happening.
Remember that lockscreen is automatically set to false when there is no
handler running, so unlerss you have an intensive handler running, you
will see these changes.
If it's not that - could you describe how you are verifying the effect
of lockscreen in more detail. Thanks.
Alex.
On 27/03/2024 22:55, Bob Sneidar via use-livecode wrote:
Hi all.
I read in the dictionary that Lock Screen does not work in Script Debug mode.
Okay so I turn it off, put the command “Lock Screen” at the entry point to a
selectionChanged handler which goes on to do a number of things that change the
appearance of the screen. The screen is decidedly NOT LOCKED! The things I go
on to do are things like changing the hilitedItems of a tab widget which in
turn shows and hides a number of objects, and also changes the selection in a
number of datagrids. Every action that alters the screen is visible after I
issue the Lock Screen command.
Is Lock Screen completely hosed? Am I missing something??
Bob S
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
