On Fri, Feb 14, 2014 at 12:19 AM, Ender Nafi Elekcioglu <endernafi@keehuna .com> 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
