Re: question re lock screen

2022-01-30 Thread William Prothero via use-livecode
Thanks, Jacqueline. That saves me some time and head scratching.
Bill

William A. Prothero, PhD
Prof Emeritus, Dept of Earth Science
University of California, Santa Barbara

> On Jan 30, 2022, at 9:58 AM, J. Landman Gay via use-livecode 
>  wrote:
> 
> Lockscreen only works within the current window, it doesn't apply to the 
> whole screen. Changing stacks will always show what's happening because LC 
> has to create a new window structure. The visibility isn't relevant per se 
> but drawing the new window is.
> 
> You can initialize the new stack before going to it. Or if you want a visual 
> effect you can go to the stack in the same window, which replaces the current 
> content with the new stack's content without creating a new window.
> 
> --
> Jacqueline Landman Gay | jac...@hyperactivesw.com
> HyperActive Software | http://www.hyperactivesw.com
>> On January 30, 2022 10:29:29 AM William Prothero via use-livecode 
>>  wrote:
>> 
>> I’m working on a transition from one stack to another, and initializing to 
>> destination stack’s screen before I show it.
>> So, my question is whether the lock screen command actually works on the 
>> invisible destination screen. Or does it only apply to a screen that is 
>> visible. How does it determine which “screen” to lock?
>> 
>> I see in the dictionary that lock screen does not work in the debug mode. 
>> Hmm…. makes it harder to debug.
>> 
>> Thanks for any info,
>> Bill
>> 
>> William Prothero
>> waproth...@gmail.com
>> 
>> 
>> 
>> 
>> ___
>> 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


___
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


Re: question re lock screen

2022-01-30 Thread J. Landman Gay via use-livecode
Lockscreen only works within the current window, it doesn't apply to the 
whole screen. Changing stacks will always show what's happening because LC 
has to create a new window structure. The visibility isn't relevant per se 
but drawing the new window is.


You can initialize the new stack before going to it. Or if you want a 
visual effect you can go to the stack in the same window, which replaces 
the current content with the new stack's content without creating a new window.


--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On January 30, 2022 10:29:29 AM William Prothero via use-livecode 
 wrote:


I’m working on a transition from one stack to another, and initializing to 
destination stack’s screen before I show it.
So, my question is whether the lock screen command actually works on the 
invisible destination screen. Or does it only apply to a screen that is 
visible. How does it determine which “screen” to lock?


I see in the dictionary that lock screen does not work in the debug mode. 
Hmm…. makes it harder to debug.


Thanks for any info,
Bill

William Prothero
waproth...@gmail.com




___
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


question re lock screen

2022-01-30 Thread William Prothero via use-livecode
I’m working on a transition from one stack to another, and initializing to 
destination stack’s screen before I show it.
So, my question is whether the lock screen command actually works on the 
invisible destination screen. Or does it only apply to a screen that is 
visible. How does it determine which “screen” to lock?

I see in the dictionary that lock screen does not work in the debug mode. Hmm…. 
makes it harder to debug.

Thanks for any info,
Bill

William Prothero
waproth...@gmail.com




___
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