Re: Lock Screen on preOpenCard

2014-02-13 Thread Ender Nafi Elekcioglu

From: Kay C Lan
> Then you don't have to bother about keeping track of pairs and can rest 
> easy at nights ...

Thank you Kay, that seems the most fail-proof solution and will definitely ease 
my mind :)

Best,

~ Ender
___
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: Lock Screen on preOpenCard

2014-02-13 Thread Kay C Lan
On Fri, Feb 14, 2014 at 12:19 AM, Ender Nafi Elekcioglu  wrote:

>
> The lock/unlock of the second card's preOpenCard handler is redundant,
> isn't it?
>
> For small or relatively simple stacks keeping track of lock/unlock pairs
is fairly straight forward. Once you get a little more complex you can run
the risk of piling up nested lock screen and then not having the visual
effect you desire when you unlock screen. I've found the easiest solution
is to:

if the lockScreen is false then lock screen

If you only ever use this then their will be no nested locked screens, so
you are only ever one command away from unlocking the screen.

if the lockScreen is true then unlock screen [with visual effect]

Then you don't have to bother about keeping track of pairs and can rest
easy at nights knowing that if left to the engine it only has to unlock
once when it goes idle - rather than having to wait a millisecond longer if
you had dozens of nested lock screen piled up.
___
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: Lock Screen on preOpenCard

2014-02-13 Thread Ender Nafi Elekcioglu
Thanks, John…


~ Ender


From: John Dixon John Dixon
Reply: John Dixon dixo...@hotmail.co.uk
Date: February 13, 2014 at 18:21:47
To: How to use LiveCode use-livecode@lists.runrev.com
Subject:  RE: Lock Screen on preOpenCard  
Yes Ender, it is...  

> Date: Thu, 13 Feb 2014 18:19:35 +0200  
> From: endern...@keehuna.com  
> To: use-livecode@lists.runrev.com  
> Subject: Lock Screen on preOpenCard  

> It came to my mind that the latter may be pointless,  
> former lock/unlock may encapsulate the second, hence the **pre**OpenCard.  
>  
> The lock/unlock of the second card’s preOpenCard handler is redundant, isn’t 
> it?  
>  
> Thanks,  
> ~ Ender  


___  
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: Lock Screen on preOpenCard

2014-02-13 Thread John Dixon
Yes Ender, it is...

> Date: Thu, 13 Feb 2014 18:19:35 +0200
> From: endern...@keehuna.com
> To: use-livecode@lists.runrev.com
> Subject: Lock Screen on preOpenCard

> It came to my mind that the latter may be pointless,
> former lock/unlock may encapsulate the second, hence the **pre**OpenCard.
> 
> The lock/unlock of the second card’s preOpenCard handler is redundant, isn’t 
> it?
> 
> Thanks,
> ~ Ender

  
___
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