The performance hit for those two lines will be negligable.

IMO, just as important is an old marketing adage "Perception is reality". If there are lots of screen updates in the Refresh(), the user may *think* the system is slow as they see things redraw and screen flicker. In that case, it may be better to keep the LockScreen lines.


>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>