I took it for a test drive to check out the new C++11 features they added, and while they're fun to play with, the most pleasant surprise was it feels much more responsive than VS2010. VS2010 is full of 0.5 to 1 sec lags everywhere: clicking on a menu requires half a second to show it, double clicking on a file takes over 1 second, opening an included header file can take even longer. All of the above are pretty much instantaneous in the beta. I've yet to use it with a decent sized project though...

This might prove useful: http://www.codeproject.com/dialog/dlgresizearticle.asp It'll save you the trouble of manually repositioning controls in response to WM_SIZE messages. HTH

Use the CFileDialog::GetStartPosition() / CFileDialog::GetNextPathName() functions http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html/\_mfc\_cfiledialog.3a3a.getstartposition.asp http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vcmfc98/html/\_mfc\_cfiledialog.3a3a.getnextpathname.asp HTH

One thing I suggest doing, is use Winlogon Notification Packages (assuming you're programming for an NT-based version of windows), you can listen to startup/shutdown/login/logoff and other events. Check: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secauthn/security/winlogon\_notification\_packages.asp HTH

Good point! :doh:

Try replacing: while( true ) { if( PeekMessage(...) ) with while( GetMessage(...) ) GetMessage stops the program for running while waiting for a message, while PeekMessage doesn't, and you have a loop running at full speed. HTH

Ravi Bhavnani wrote: But if I'm not mistaken, a "Run" entry in the HKEY_LOCAL_MACHINE subtree causes the application to start after any user logs in, as opposed to a corresponding entry for a specific user in the HKEY_USERS subtree which causes the app to only start when that user logs in. Regardless, the user has to first login. That's the way I've taken it to work, I always have to log in of HKLM\...\Run to take effect. One thing I suggest doing though, is use Winlogon Notification Packages (assuming you're programming for an NT-based version of windows), you can listen to startup/shutdown/login/logoff and other events. Check: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/secauthn/security/winlogon\_notification\_packages.asp HTH