lock screen question

[Eric Chatonet]

Bonsoir Tom,

In my experience, even if the engine unlocks screen at the end of a  
handler, I always prefer to do it myself when appropriate (even at  
the end of the handler), especially on Mac OS X:
You'll see that your app's 'reactivity' will appear far better.

Le 22 avr. 08 à 21:31, Thomas McGrath III a écrit :

> Bonjour Eric,
>
> That is good to know but makes me question what or how the screen  
> still unlocks at the end of a handler even though I have not put an  
> unlock screen in there??? I will clean up my pairs anyway.
>
> Thanks again,
>
> Tom
>
> On Apr 22, 2008, at 12:34 PM, Eric Chatonet wrote:
>
>> Bonjour Thomas,
>>
>> Actually, lock and unlock screen work as a pair:
>> They are 'stacked'.
>> This means that after two 'lock screen', an 'unlock screen' is not  
>> enough to unlock screen: you need two of them.
>> Parity between lock and unlock screen is compulsory :-)
>> If you are lost you can use:
>>
>> on UnlockScreen
>>  repeat until not the lockScreen
>>    set the lockScreen to false
>>  end repeat
>> end UnlockScreen
>>
>> Or the opposite, of course...

Best regards from Paris,
Eric Chatonet.
----------------------------------------------------------------
Plugins and tutorials for Revolution: http://www.sosmartsoftware.com/
Email: eric.chatonet at sosmartsoftware.com/
----------------------------------------------------------------