Labwindows/CVI applications & stealing focus

[LuisG]

CVI hasn't used the SetForegroundLockTimeOut registry value in a while. That option was originally used to control whether to display a dialog, at startup, to give users the option to change the foreground lock timeout permanently (so as to enable bringing the ADE to the foreground as needed, during debugging). The way it's supposed to work since that dialog was removed is for CVI to always temporarily change [HKCU]\Control Panel\Desktop\ForegroundLockTimeout to 0, while it's debugging a program, and then to restore it to what it had been, once the debugging ends.

I've just tested this in Windows 7 by artifically changing the value of [HKCU]\Control Panel\Desktop\ForegroundLockTimeout to some random value and then debugging a problem, and what I'm seeing is that CVI changes it to 0 but then does not restore it to what it had been. I assume that this is also what you're seeing. This is unexpected and it seems to be a bug. This code in CVI hasn't changed, so I'm not sure if something changed in the OS. I can't explain why this is now broken.

I've created a bug report (ID: 316246) to investigate this further. Sorry about the inconvenience.

Luis

[tstanley]

Hi,

Thanks for looking into this.  That's the behavior I have been noticing.  It would be nice if there was an option to completely disable CVI's setting of the ForegroundLockTimeout as personally I think it's annoying and potentially creates an unnessecary difference (though minor) between the development machine and the machines the application is deployed on, but I suppose I can live with it.