Beg to disagree - Craig's code is fine

Suppose a control on the form - say a grid - also sets and resets LockScreen in its Refresh()

Thisform.Refresh() triggers grid.Refresh()

If LockScreen is true when the grid does its Refresh(), it should not set it to false upon exit

___

>I don't see how your code makes this less dangerous. If I always unlock the screen after .Refresh() then I am already doing it as safe as possible. The only thing your code will do is possibly leave the screen in locked state (if prior to this code the screen was locked) and this could be harmful. Thank you.
>
>>IMO, that's dangerous code. Always save the current value going in and reset to that going out, so the code would look like:
>>

>>llLockScreen = ThisForm.LockScreen
>>ThisForm.LockScreen = .T.
>>ThisForm.Refresh()
>>ThisForm.LockScreen = llLockScreen
>>

>>
>>>Hi,
>>>
>>>When I started developing in VFP (I think around 1998) I read somewhere that it is a good idea to call .LockScreen .T. before calling form.refresh(). So I have in a lot of places in my application call to method Thisform.MyRefresh(). And the code in the MyRefresh() is
>>>
>>>

>>>thisform.Lockscreen = .T.
>>>thisform.refresh()
>>>thisform.Lockscreen= .F.
>>>

>>>
>>>Does it still make sense to keep this code? Or with the hardware we have today the refresh is just as fast with or without Lockscreen?