Click here to Skip to main content
15,899,555 members
Home / Discussions / C / C++ / MFC
   

C / C++ / MFC

 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Graham Breach30-Jul-21 8:17
Graham Breach30-Jul-21 8:17 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
ForNow30-Jul-21 8:28
ForNow30-Jul-21 8:28 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Graham Breach30-Jul-21 8:49
Graham Breach30-Jul-21 8:49 
AnswerRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Richard MacCutchan30-Jul-21 4:56
mveRichard MacCutchan30-Jul-21 4:56 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
ForNow30-Jul-21 5:11
ForNow30-Jul-21 5:11 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Richard MacCutchan30-Jul-21 5:28
mveRichard MacCutchan30-Jul-21 5:28 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Dave Kreskowiak30-Jul-21 6:10
mveDave Kreskowiak30-Jul-21 6:10 
GeneralRe: Handling KeyBoard messages/accelerators handling in MFC dialog based applications Pin
Richard MacCutchan30-Jul-21 6:15
mveRichard MacCutchan30-Jul-21 6:15 
QuestionDynamically creating CToolBar Pin
Benjamin Bruno30-Jul-21 3:54
Benjamin Bruno30-Jul-21 3:54 
AnswerRe: Dynamically creating CToolBar Pin
Richard MacCutchan30-Jul-21 4:52
mveRichard MacCutchan30-Jul-21 4:52 
QuestionRGB image to CMYK gdi+ Pin
Gopi Nath15-Jul-21 22:25
Gopi Nath15-Jul-21 22:25 
AnswerRe: RGB image to CMYK gdi+ Pin
Richard MacCutchan17-Jul-21 6:15
mveRichard MacCutchan17-Jul-21 6:15 
AnswerRe: RGB image to CMYK gdi+ Pin
RedDk16-Oct-21 8:24
RedDk16-Oct-21 8:24 
QuestionException handler Pin
Drugodrf14-Jul-21 6:39
Drugodrf14-Jul-21 6:39 
AnswerRe: Exception handler Pin
Greg Utas14-Jul-21 9:15
professionalGreg Utas14-Jul-21 9:15 
AnswerRe: Exception handler Pin
SeeSharp214-Jul-21 10:31
SeeSharp214-Jul-21 10:31 
GeneralRe: Exception handler Pin
Drugodrf15-Jul-21 6:15
Drugodrf15-Jul-21 6:15 
GeneralRe: Exception handler Pin
Victor Nijegorodov15-Jul-21 9:25
Victor Nijegorodov15-Jul-21 9:25 
GeneralRe: Exception handler Pin
jschell17-Jul-21 9:38
jschell17-Jul-21 9:38 
GeneralRe: Exception handler Pin
Victor Nijegorodov17-Jul-21 9:51
Victor Nijegorodov17-Jul-21 9:51 
GeneralRe: Exception handler Pin
Richard MacCutchan17-Jul-21 21:08
mveRichard MacCutchan17-Jul-21 21:08 
QuestionC++ Pin
Member 152817338-Jul-21 8:52
Member 152817338-Jul-21 8:52 
AnswerRe: C++ Pin
OriginalGriff8-Jul-21 8:56
mveOriginalGriff8-Jul-21 8:56 
Compiling does not mean your code is right! Laugh | :laugh:
Think of the development process as writing an email: compiling successfully means that you wrote the email in the right language - English, rather than German for example - not that the email contained the message you wanted to send.

So now you enter the second stage of development (in reality it's the fourth or fifth, but you'll come to the earlier stages later): Testing and Debugging.

Start by looking at what it does do, and how that differs from what you wanted. This is important, because it give you information as to why it's doing it. For example, if a program is intended to let the user enter a number and it doubles it and prints the answer, then if the input / output was like this:
Input   Expected output    Actual output
  1            2                 1
  2            4                 4
  3            6                 9
  4            8                16
Then it's fairly obvious that the problem is with the bit which doubles it - it's not adding itself to itself, or multiplying it by 2, it's multiplying it by itself and returning the square of the input.
So with that, you can look at the code and it's obvious that it's somewhere here:
C#
int Double(int value)
   {
   return value * value;
   }

Once you have an idea what might be going wrong, start using the debugger to find out why. Put a breakpoint on the first line of the method, and run your app. When it reaches the breakpoint, the debugger will stop, and hand control over to you. You can now run your code line-by-line (called "single stepping") and look at (or even change) variable contents as necessary (heck, you can even change the code and try again if you need to).
Think about what each line in the code should do before you execute it, and compare that to what it actually did when you use the "Step over" button to execute each line in turn. Did it do what you expect? If so, move on to the next line.
If not, why not? How does it differ?
Hopefully, that should help you locate which part of that code has a problem, and what the problem is.
This is a skill, and it's one which is well worth developing as it helps you in the real world as well as in development. And like all skills, it only improves by use!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!

QuestionRe: C++ Pin
David Crow8-Jul-21 12:19
David Crow8-Jul-21 12:19 
AnswerRe: C++ Pin
Richard MacCutchan8-Jul-21 21:10
mveRichard MacCutchan8-Jul-21 21:10 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.