>>>>>What harm would it cause if after grid does Refresh() it sets the Lockscreen to false?
>>>>
>>>>Harm ? none - LockScreen won't be set any longer. But then, if that is the line of reasoning, why use it in the first place ?
>>>>
>>>
>>>Exactly my point :)
>>
>>You've lost me
>
>Craig's point was that without saving the Lockscreen condition the code would be dangerous. My point that adding code that stores and restores the Lockscreen condition does not make the code less dangerous.

It's not dangerous, but it's not optimum either

And wasn't the whole intent to optimize ?

It's not dangerous in this context - but that way of programming is dangerous