|
Yes, that's one of the reasons you never need a code obfuscator for ATL sources...If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Nice joke 
|
|
|
|
|
It was? 
 You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists.
|
|
|
|
|
When I excute the developing program in VC6.0 debugging enviroment,the program run successfully.But when I excute the program of release version alone,appear the error infomation below:
microsoft Visual C++Runtime Library
Runtime Error!
Program: C:\Progra....
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
However,the program of previous release version excute successfully.why?
I need your help and suggestion,thanks.
|
|
|
|
|
onlysaint wrote: When I excute the developing program in VC6.0 debugging enviroment,the program run successfully. But when I excute the program of release version ...
microsoft Visual C++Runtime Library
Hi,
Please take a look at this article: www.flounder.com/debug_release.htm[^]
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
thanks for your suggestion,I hope some realistic operations to solve my question.
|
|
|
|
|
Firstly, both the debug builds and the release builds should be built with debug information. Some people erroneously believe that only release debug builds can be built with debugging information, but this simply isn't the case. Assuming you've got a release build with symbol files then proceed as you always would; break into the application with a debugger when the fault occurs and get a stack trace.Steve
modified on Tuesday, March 2, 2010 8:30 PM
|
|
|
|
|
Stephen Hewitt wrote: Some people erroneously believe that only release builds can be built with debugging information, but this simply isn't the case.
Umm... Surely, you wanted to say 'debug builds' instead?
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
| Yeah, that's what I meant. Steve
|
|
|
|
|
Could you give me some advices to solving the problem,thanks very much!
|
|
|
|
|
| I thought I did. I'll reiterate: Firstly ensure that the release build is built with debugging information. Then run the program under a debugger, break execution when the problem occurs and get a stack trace. Pick the thread that's displaying the runtime error message. Which part of this are you having problems with? Steve
|
|
|
|
|
Dear All,
I am working on Exporting different compressed format(Mjpeg,H264,Mpeg4)files into AVI container.
I have included vfw.h and vfw32.lib.And,using AVIFileCreateStream,AVIStreamWrite to create and write into AVI container.
Here,AVIStreamWrite method returns E_UNEXPECTED.
Im not able to proceed further.Also,i could not find the reason for this error.
I have searched in google.Many samples which do the export from BMP to AVI are available.
Could any one of u help me ?
I am new to this video and audio format..
Thanks,
Gomathy L.
|
|
|
|
|
Hi
Im having the same problem as you where having with AVIStreamWrite. Im trying to write MJPG frames from an IP camera into a AVI container. Did you ever solve your problem?
Thanx
|
|
|
|
|
Hi,
Yes.I have solved that problem and now I have implemented AVIStreamWrite for Mjpg,mpeg4,H264…
Actually,If that returns E_UNEXPECTED means,the codec which we r using is not correct.
I have followed this link. http://www.morgan-multimedia.com/download/codec.c
Pls,go thro it.
Regards,
Gomathy L.
|
|
|
|
|
|
I think my problem is that im not specifying the correct format of the incoming MJPG stream and therefore when I create the avi I either get an error or a black video depending on the codec I use.
|
|
|
|
|
Yes..Obviously.
AVISTREAMINFO streamInfo;
memset(&streamInfo, 0, sizeof(streamInfo));
streamInfo.fccType = streamtypeVIDEO;
streamInfo.fccHandler = mmioFOURCC('M', 'J', 'P', 'G');
streamInfo.dwScale = 1001;
streamInfo.dwRate = 30000;
streamInfo.dwSampleSize = 1;//0;
streamInfo.dwSuggestedBufferSize = 0 ;
SetRect(&streamInfo.rcFrame, 0, 0,frameInfo.m_width,frameInfo.m_height);
try this..
|
|
|
|
|
Brilliant!! It worked
One more thing, What number do I need to use for dwRate to change the frame rate to 25 fps?
Thank you.
|
|
|
|
|
Just give dwRate as 1..hope it will work.. 
|
|
|
|
|
Hi all,
I have one project which should done in vC++.
We need to Implement An activex component in vc++.
if ur interested we can discuss on that by mail.
Thansk
Kishore
|
|
|
|
|
You should try it in the job offers section[^].Regards.
--------
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpfull answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Hi,
I have a simple VS2008 C++ MFC application that shows a FormView in which a "Microsoft Office Spreadsheet 10.0" has been inserted. At this point when the program is runing I can manually manipulate -but ONLY with the keyboard! the spreadsheet cells like a usual Excel one.
Now I would like to do the same programatically but I don't know how!
I have added a variable to the component and this variable seems to let me control the spreadsheet through a LPDISPATCH pointer.
This is the instruction that VS2008 automatically put in the DODataExchange() function:
DDX_Control(pDX, IDC_SPREADSHEET1, in_grid);
in_grid is name of the variable added to "SPREADSHEET1" component.
Later in the code I have this instruction:
LPDISPATCH lpd_grid = in_grid.get_ActiveSheet();
Most of functions avalable through in_grid return this type LPDISPATCH. But I have not undestood how I can use this pointer to Write/Read the cell's value.
In so many exemples found here and there LPDISPATCH lpd_grid would be used in this way:
Excel::_WorksheetPtr xlWs = in_grid.AttachDispatch(lpd_grid);
but in the present case the later instruction above would lead to a compiler error.
Does anybody ever used this "Microsoft Office Spreadsheet 10.0" ?
Regards
Bernard
|
|
|
|
|
I need some hint / help in troubleshooting this error.
It gets retruned by both WriteFile and ReadFile when writting to or reading from file opened for asynchronous ( COM port ) access.
The file is created using
m_hCOM = ::CreateFile(lpszDevice, // COMx
GENERIC_READ|GENERIC_WRITE,
0, // exclusive
0, // security irrelevant
OPEN_EXISTING, // it has to be there
FILE_FLAG_OVERLAPPED, // asynchronous
0); // template file
And this is wherw it fails
// write to comm port
iResult = WriteFile(m_hCOM, (char*) data, dwSize, &dwWritten, &osWrite);
with this cryptic error message
"Invalid access to memory location"
DCB, mask and timeouts are properly configured.
At this time I am wiriting single (dwSize = 1) null '0' character and the OVERLAPPED structure event is set.
I am obviously missing something.
Any constructive help as always is appreciated. Suggestions to copy someone else code are not necessary. Been there - done that.
Vaclav
-- Modified Monday, March 1, 2010 11:06 PM
|
|
|
|
|
What is data?
How is it defined? How is a value associated with it?
From what you posted, it seems likely that there is something wrong with your use of (char*) data. Of course, there isn't enough in your post to say for sure.Please do not read this signature.
|
|
|
|
|
Thanks for reply. I must have had something wrong with the setup parameters, I have rebuild my code using defaults and this problem went away. Even if I set the data entry to NULL, the WriteFile still works without his access memory error. It returns zero characters written as expected.
Now I need to find out why the WriteFile fails - return 0, but the last error is not ERROR_IO_PENDING as expected, but no error whatsoever. For now I will work on that.
Thanks again for your helpfull suggestion.
Vaclav
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
