>>>>>>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
In general I agree that saving and restoring a condition is a good practice. But my initial question was whether locking screen (via Lockscreen) is worth the two lines of code, in terms of performance improvement. Adding the code of saving the Lockscreen only adds to the .EXE bloat <g>
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
