|
Hello,
Did you port some old code written in a different language that are not part of a standard library? If so, and they are called from IOschermclass, try not to call those.
The is a tiny change that this will help you getting closer to the source of your problem...
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
No,
it's all fesh, brand new code, written in MFC C++ in vStudio .NET 2003
|
|
|
|
|
If you press other bottons on the dialog, do you get the same error?
jij bent trouwens de eerste nederlander die ik hier tegenkom 
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
No, i don't get the same error : it's unique
Nee hoor, ik krijg niet dezelfde error, dit gebeurt alleen bij die specfieke knop.
|
|
|
|
|
Post the code for the OnCancel() method, the problem probably lies there
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
I mean the OnBnClickedCancel() method,...
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
it's just EndDialog(IDCANCEL);
|
|
|
|
|
When I look at the declaration of EndDialog, you are missing a parameter! (from the msdn library: BOOL EndDialog(HWND hDlg, INT_PTR nResult);)
but let's get something straight:
When you press the cancel button, OnBnClickedCancel() is called.
From there you call EndDialog().
Assuming this, maybe you should call CDialog::OnCancel(). The EndDialog function just ends the message loop returning control to the system, maybe something goes wrong there.
A student knows little about a lot.
A professor knows a lot about little.
I know everything about nothing.
|
|
|
|
|
OK,
I'll try: wait a moment
|
|
|
|
|
I'm sorry, doesn't work
DO you have got some other idea's
I'll put the code of my first window, wich will have to receive the message, below this text.
void CF2FDlg::ga_naar_IOscherm(Cmodeprop C)<br />
{ <br />
IOschermclass *iosclass;<br />
iosclass=new IOschermclass();<br />
iosclass->set_properties(C);<br />
<br />
INT_PTR nRet = -1;<br />
nRet=iosclass->DoModal();<br />
<br />
<br />
<br />
switch(nRet)<br />
{<br />
case IDCANCEL:<br />
{<br />
return;<br />
}<br />
case IDC_stop:<br />
{<br />
break;<br />
}<br />
<br />
case 1:<br />
{<br />
return;<br />
}<br />
default:<br />
{<br />
return;<br />
}<br />
};<br />
<br />
<br />
return;<br />
}<br />
|
|
|
|
|
I'm sorry, doen't work
DO you have got some other idea's<br />
<br />
I'll put the code of my first window, wich will have to receive the message, below this text.<br />
<br />
<br />
void CF2FDlg::ga_naar_IOscherm(Cmodeprop C)<br />
{ <br />
IOschermclass *iosclass;<br />
iosclass=new IOschermclass();<br />
iosclass->set_properties(C);<br />
<br />
INT_PTR nRet = -1;<br />
nRet=iosclass->DoModal();<br />
<br />
<br />
<br />
switch(nRet)<br />
{<br />
case IDCANCEL:<br />
{<br />
return;<br />
}<br />
case IDC_stop:<br />
{<br />
break;<br />
}<br />
<br />
case 1:<br />
{<br />
return;<br />
}<br />
default:<br />
{<br />
return;<br />
}<br />
};<br />
<br />
<br />
return;<br />
}<br />
|
|
|
|
|
I just solved the problem... I thought you might like to know how I did it,, but I don't understand it myself --> when I removed the setproperties call, everything worked okay.
The program must have had the problems because of that crash, although it is just a very simple function:
Th second screen has an own object of type Cmodeprop, with setproperties you povide an object to get passed to the second window. It is something like this:
set_properties (Cmodeprop C)<br />
{<br />
own_props=C;<br />
return;<br />
}
This is really strange (microsoft!!!)
|
|
|
|
|
That sure is strange! Well, At least you solved it!  .
I once had a strange assertion in my program. It took me 3 days to solve it  !
(by the way, Cmodeprops is probaly a class, did you write a copy constructor? or overload the operator=? It might solve something!)
Good luck...
|
|
|
|
|
Hello,
I had a similar error. Try "Rebuild All"
|
|
|
|
|
Let me try........
No doesn't work:
I've pressed clean solution under BUILD, ad then Rebuild Solution. After trying again I got the same error
|
|
|
|
|
It is strange
Difficult say more without seeing project settings and code...
Vitali
|
|
|
|
|
I've put some code on this forum (this thread at 8:37), please take a look
|
|
|
|
|
Thakns, but I don't think this will make a change ?
|
|
|
|
|
Normal code;)
Some comment:
Replace :
IOschermclass *iosclass= new IOschermclass();
INT_PTR nRet = -1;
nRet=iosclass->DoModal();
to
IOschermclass iosclass;
int nRet=iosclass.DoModal();
May be you doing "something artful" in this dialog?
Vitali
|
|
|
|
|
I am building a MFC based program that will first run a series of pings and then NET VIEW command to see which users are online. I have already been able to create a process to run ping.exe, but how can I run NET VIEW and capture the output? I've been digging information, and my head is spinning. Not even coffee helped :P How to capture output from CreateProcess()?
|
|
|
|
|
Поцелуй свой поток в зад!!!
|
|
|
|
|
Use a Pipe to redirect the output to your window;
See CreatePipe, STARTUPINFO and CreateProcess.
Arjan.
|
|
|
|
|
Thank you for the reply. It led me to find an article named "Creating a child process with redirected input and output", which is exactly what I wanna do 
|
|
|
|
|
Hi,
I'm studying C++, VC++, COM. I would like to know real world examples of various assignments programmers have worked on. For example, what the application did what role did they play. The examples would be using these kinds of technologies. If any programmers could provide some insight into their "real world VC++, MFC, COM experiences it would be very helpful. Any one who has worked on large scale apps, developing controls, database interfaces, or anything else they have done using these technologines, who can lend some insight into how they real world of programming is.
|
|
|
|
|
My first "real" job was in a manufacturing environment, (before C++ and MFC was even a smile on someone's face), where numerically controlled machine tools produced parts for larger assemblies. Since each machine had a special set of codes that caused it to perform specific actions, there was a compiler that would translate the commands to create a part into the machine codes to control the machine.
My job as a programmer was to "update" the compiler and make it work on the new computing platform that was being installed as part of the shop floor overhaul. The legacy code was written in FORTRAN IV, and we were also updating it to F77 on the new computer, in addition to cleaning up as much of the "bad" software as we could. Ever done string processing in FORTRAN? Ouch!!
Since the new computer was much newer than the computer that ran the legacy code, there were some new options available for producing graphics, so I also developed a graphical display of the paths that the machines would follow given the codes that were produced from the compiler for the parts that were being made. Reviewing the graphics output saved the time and trouble of setting the machines up to create a test piece, to see if the part program was really correct.
That was only my first job, and it lasted several years. Much of the experience, though, wasn't so much about programming as it was about manufacturing. The compiler and graphics software never stood on its own, but was an integral part of the manufacturing process. That process had to be understood to make the software fit in.
Very good question, too, and I hope you get some good stories and insights.
Dave
"You can say that again." -- Dept. of Redundancy Dept.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
