Re: When presses ENTER on Edit BOX

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Those, and the TRACE outputs built into MFC.

I just debugged a lexer in about an hour using some nice debugging features that took very
little time to add. I'm about to start debugging the parser, and next the interpreter. I
would not attempt to handle these without a decent tracing facility.
joe

On Thu, 7 Sep 2006 07:48:25 -0700, "Tom Serface" <tserface@xxxxxxx> wrote:

Some of the messages can be very helpful. For example, we're testing a new
release of our software right now. One of the testers found a problem that
he could easily reproduce, but I couldn't reproduce it here. I "finally"
figured out the difference in our systems and the first time I ran a debug
build an assert popped up identifying the offending line of code. A quick
review of the code revealed the problem in no time. That "mechnism" saved
me a few hours time over how I had to do things in the old days which was
basically guess where the problem might be and hope that I could narrow it
down with some pop up messages of my own design. The messages the debugger
(and OS) pop up can be your friends...

Tom

"Joseph M. Newcomer" <newcomer@xxxxxxxxxxxx> wrote in message
news:u9a0g2pd2mb7krlb2q8i5crsk9ovgnltu0@xxxxxxxxxx
It's one of the things I teach my students...make any odd
resource-name-change, and
Rebuild All is the best and safest approach to the next build.

I wonder if some of the people looking at these error boxes actually
bother to *read* the
text. Do they really think the *buttons* carry all the important
information? Admittedly,
sometimes the text is not entirely obvious to a novice, but that's why
they're asking the
question here. If they give the text, then we can explain "When you see
that message it
means..." and they might actually *learn* something. But apparently when
anything happens
that pops up a MessageBox, their brains shut down and all they can think
to do is dismiss
the MessageBox without actually reading it, usually by clicking the
"abort" button. This
is not a constructive approach to debugging. And it is not a practical
approach to asking
for help. The question which can be summed up in its entirety as "my
program doesn't
work, what did I do wrong?" deserves whatever scorn can be heaped on it.
joe

Joseph M. Newcomer [MVP]
email: newcomer@xxxxxxxxxxxx
Web: http://www.flounder.com
MVP Tips: http://www.flounder.com/mvp_tips.htm
.

Relevant Pages

  • Re: Is this bug of VC?
    ... either with debugging or without debugging, the path of disk in the returned string ... MVP Tips: http://www.flounder.com/mvp_tips.htm ...
    (microsoft.public.vc.mfc)
  • Re: Is this bug of VC?
    ... either with debugging or without debugging, the path of disk in the returned string is lower-case character "c:\", but when I run it from windows explorer,or any other ...
    (microsoft.public.vc.mfc)
  • Re: Forms authentication annoying password prompt!
    ... Joe Kaplan-MS MVP Directory Services Programming ... Co-author of "The .NET Developer's Guide to Directory Services Programming" ... I get the follwing error message when I try to run the ... Debugging Failed Because Integrated Windows Authentication Is Not ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • RE: Logging
    ... \par The log file you mentioned includes some error message but may did not helpful for you to debugging. ...
    (microsoft.public.sharepoint.portalserver.development)
  • Re: Is this bug of VC?
    ... anything that depends on case-sensitivity. ... Fix your program. ... either with debugging or without debugging, the path of disk in the returned string ...
    (microsoft.public.vc.mfc)