>I have run my old application and the new application side by side, >stepping through the code. Everything seems to be the same.. window >styles are the same, all other parameters are the same except for things like >pointer values and handle values. My old version works fine and the >::CreateWindowEx call returns a valid hWnd. The new version of the >application returns a NULL hWnd at the same source code line. > >Windows won't allow me to step into ::CreateWindowEx to see what >exactly is going on. >We have tried a full rebuild of the code, and tried running it on a different PC. >Neither helped. What could be the problem or solution?
Any idea what the changes were that were made by your colleague? If they aren't too numerous, the thing to do would be to undo the changes one at a time until it starts working again (hopefully!), see if you can pinpoint which change caused it. Trying to narrow the search area HAS to be the first step. There are many hidden factors that can cause a behaviour change in controls / windows... an updated manifest file on XP specifying different control versions, an overridden method or message handler in the class affecting how / whether it gets created (especially for a dialogue or view), subclassing / overriding WindowProc()s, the registered window class being altered (if not using default MFC window classes), even a change in the parent window that may affect how its child controls / windows get handled - all things which don't show directly in the line of code that actually tries to create the window / control in question. -- Jason Teagle [EMAIL PROTECTED] _______________________________________________ msvc mailing list msvc@beginthread.com See http://beginthread.com/mailman/listinfo/msvc_beginthread.com for subscription changes, and list archive.
