Have you messed with (i.e., deleted, renamed) any of your project's menus?
Have you looked in any of MFC's DOC*.CPP files to see what condition causes the AFX_IDP_FAILED_TO_CREATE_DOC message to be displayed?
"Normal is getting dressed in clothes that you buy for work and driving through traffic in a car that you are still paying for, in order to get to the job you need to pay for the clothes and the car and the house you leave vacant all day so you can afford to live in it." - Ellen Goodman
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
Adding/repeating the article linked:
Race condition is the most likely, if your code includes a chance for that.
Second-highest chance goes to uninitialized variables or using uninitialized pointers, the change caused by different memory initializations.
You are working at different memory locations depending on running under the debugger or as standalone (even ctrl+F5 vs. double-clicking the exe can show differences...). Normally, in debug builds, memory locations are initilized to the same value, but there are loopholes.
Did you check the return value of SendDlgItemMessage?
Also, there are some patterns to avoid or use when sending messages, especially when focus involved, e.g. changing focus during a focus change message never works correctly.
When running under the debugger step by step, your application will get (and handle) additional killfocus and setfocus messages. Which might at least explain the difference.
The compiler is buggy, so if you've tweaked any of the compiler knobs first untweak them. The defaults are the safest & most reliable.
Next, do a full rebuild regardless. Out of sync object files create a variety of mysterious problems.
Assuming a clean build, you might be getting an exception that's masked by the breakpoint trap. I'd probably brute force debug this by just adding TRACE statements to narrow down where the error occurs.
I have an application that has a ListCtrl. After creating a new dialog over the ListCtrl, and if I close the dialog by Cancel or OK button, there is a shadow that has the Windows dialog classic color covering some part of the ListCtrl. For columns on the ListCtrl, I can just put the cursor over it and then the text is shown automatically. For Items, I have to Left click them to get them displayed.
Also, if I minimize the application and restore it again, the whole part of the ListCtrl is covered by the windows classic color.
My system is Windows XP in Classic theme.
Thanks for any idea or help about this.
Toe the line
Thread the needle
Think outside of the box
hello , i've tryed to capture snapshots on yahoo webcam with bitblt to make a yahoo webcam recorder, i managed to do it but with some problems. on my webcam it works perfectly the image captured is clear but if i try to snapshot another webcam window(some work some don't) the image is scrambled. i will post the entire source code it's not too long and a sample snapshot to see the problem.
I don't have an old TV or a cracked LCD display to compare to.
Can you post an example image somewhere?
If it works on some windows and not others, then I imagine it's
a problem with the way the video is being rendered (DirectX,
for example), you're scraping the screen out of sync with the video
refresh, or you're getting frames in between key frames.
nope same problem and getlasterror still returns Not enough storage after the CreateDIBsection func. i think there is the problem maybe i miscalculated something on the bitmap structures , what do you think ?
P.S : thanks for your kindness to help me
Last Visit: 31-Dec-99 19:00 Last Update: 5-Feb-23 13:50