|
You have to first close your dialog using OnCancel()/OnOK(). Then you can terminate your application from your main class.
void MyClass::OnSomeAction()
{
CMyDlg dlg;
dlg.DoModal();
//The thread is blocked at this point, and will resume only if the dialog is dismissed
//Terminate the application here.
}
"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."
|
|
|
|
|
dear all
can a single CDialog based class be associated with 2 dialog resources....
if yes how
regards
rIsHaBh
|
|
|
|
|
|
It can be done like this:
pDialog = new CMyDialog();
//Check if new succeeded and we got a valid pointer to a dialog object
if(pDialog != NULL)
{
BOOL ret = pDialog->Create(IDD_MYDIALOG,this);
//Change IDD_MYDIALOG with another resource ID
if(!ret) //Create failed.
AfxMessageBox("Error creating Dialog");
pDialog->ShowWindow(SW_SHOW);
}
"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."
|
|
|
|
|
Dear all
CString aStr="Learning 中文"; //a mixed English and Chinese string
Without using Unicode, How can i extract the Chinese Character word by word from a Mixed English and Chinese string?
Thanks
|
|
|
|
|
To find the double-byte characters, step through one char at a time and call IsDBCSLeadByte() on each one. When that function returns true, that char and the following one make up one double-byte character.
|
|
|
|
|
Thank you.
can you tell me how to make a one double-bye character?
|
|
|
|
|
|
finite state machine...
recognize the pattern 10110 in the user inputted string..
also handle overlapping if any...like hav to check for aal possible occurrences of this pattern...this pattern 10110 is hardcoded...
Avoid using if else...
use function pointer...
so any one who can help and give me the code for this in C++ i be grateful 2 u...
|
|
|
|
|
|
This looked like a fun little project to create, so I took about 15 minutes of my time to write this. I'm not going to post the code (which was 29 lines from start to finish, including the #include statements.) I'm not sure if my approach is what you are looking for, but I set aside 5 variables (I made an array to hold these) of type unsigned short. Then I just wrote a for loop which looked at each character of the input string and added it to each variable (you have to reset one of the variables back to zero each pass through the loop, just use the mod operator.) At the end of my for loop I looked at my variable that I'm going to reset the next time through my loop (it should contain 5 characters by now) and if the bit pattern in this variable is the same as the bit pattern you are looking for, then it outputs the place in the string where this pattern came from. That's it!
Give this a try for a while and if it's killing you then post a reply to my message and I'll post you the code (I don't mind helping people with homework.) I wanted you to try it first since I gave you some ideas on how to approach this. Hopefully I wasn't too vague but I don't want to give away the entire solution right away! 
Good luck!
Douglas A. Wright
dawrigh3@kent.edu
|
|
|
|
|
Hi! I have been assigned to design a database program that is capable of reading a barcode via a barcode device. The problem is, I have never done anything involving serial ports. Are there any good tutorials about serial ports or could you point me in the right direction by listing a few of the functions involved?
-- Steve
|
|
|
|
|
To open a COM port, you can use the CreatFile( ... )
To access COM port properties, use GetCommProperties(...)
To write to a COM port, use WriteFile(...)
see this link:
http://www.control.com/966781257/index_html
"A robust program is resistant to errors -- it either works correctly, or it does not work at all; whereas a fault tolerant program must actually recover from errors."
|
|
|
|
|
I have the following code:
<br />
void* fixaddr;<br />
DWORD delta<br />
.<br />
.<br />
.<br />
<br />
*((WORD *)fixaddr) += HIWORD(delta);<br />
.<br />
.<br />
.<br />
During compilation I get the following error:
warning C4244: '+=' : conversion from 'int' to 'unsigned short', possible loss of data
Since I don't want any warnings appear in my code I wonder how to fix this ?
|
|
|
|
|
You could turn down the warning level 
|
|
|
|
|
cast HIWORD result to WORD:
*((WORD *)fixaddr) += (WORD)HIWORD(delta);
|
|
|
|
|
Which makes little sense since the HIWORD() macro already casts its result to a WORD. The int that the compiler is complaining about is on the left of the += operator, not the right.
Five birds are sitting on a fence.
Three of them decide to fly off.
How many are left?
|
|
|
|
|
I don't understand why, since the expression on the left IS a WORD. And we have no knowledge of this HIWORD macro; it maybe does not cast to a WORD.
|
|
|
|
|
I have reduced warning level to 3, and this warning does not appear.
Thanks for help!
|
|
|
|
|
Which does nothing but mask this and other potential problems. Leave the compiler warning level at 4 and fix the problem correctly. The compiler generates warnings/errors for a reason. If something wasn't suspect, there'd be no reason to warn you.
Five birds are sitting on a fence.
Three of them decide to fly off.
How many are left?
|
|
|
|
|
How refreshing! It's not just me that works that way, then 
(The more of your replies I read, the more I wish you worked at the same place I do...) [fx: toadying mode off]
Steve S
|
|
|
|
|
 Hi, newbie here,
I was wondering what's the best way to use the CMemoryState object to check for memory leaks in a MFC program.
I want to set a checkpoint at the very beginning of the program and the very end, so in what functions should I call
oldState.Checkpoint() and newState.Checkpoint()?
|
|
|
|
|
Call the CheckPoint() method of a CMemoryState object where you want to start tracking. At the point where you want to stop tracking, call the CheckPoint() method of a second CMemoryState object. Then, call the Difference() method of a third CMemoryState object, passing to it the other two CMemoryState objects.
Five birds are sitting on a fence.
Three of them decide to fly off.
How many are left?
|
|
|
|
|
I know how to use the functions, I want to know where is the best place to call them in the App.
I was calling the oldState.Checkpoint() in the App() and
newState.Checkpoint() in App::ExitInstance() but it returned a difference.
When I called oldState.Checkpoint() it listed (I think) a CDocTemplateManager object and a CSingleDoctemplate object.......
So this is obviously not the best place to call oldState.DumpAllObjectsSince() to check overall memory usage.
Is there a function after App::ExitInstance to do the difference check in?
|
|
|
|
|
Generally speaking, in a DEBUG build you'll get this behaviour anyway providing your CPP files have the '#define new ....' stuff in them.
Are you calling CheckPoint before or after calling the base ExitInstance()?
Steve S
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
