LockScreen speeds native VFP updates* --*- set THISFORM.LockScreen True
before updating or refreshing the form, then LockScreen False when all
changes are completed. FoxPro repaints the screen once instead of many
times, actually speeding up the application. This also provides a
psychological
Derek Kalweit wrote:
And if your LockScreen=.F. commands are causing flashy
updates(particularly image controls with alpha channels), here's a
work-around for that too. Create a Lockscreen_assign method, and use
this code:
LPARAMETERS tlNewLockScreen
IF tlNewLockScreen Then
Note that the API function needs to be defined ahead of time:
DECLARE INTEGER LockWindowUpdate IN user32 INTEGER hWndLock
Cool! What's your preference of where you'd declare that?
I declared it in load event of the one form I had to implement this
in, as init wasn't soon enough. It might
Many already know this, but for some who may not, I stumbled across
Ted's whitepaper notes from DevCon '04 that gives tips on improving
performance (or at least perceived performance) while searching for
issues with multiple, nested LockScreens.
4 matches
Mail list logo
