Article View: comp.windows.ms.programmer
Article #1581Re: Borland C++ Debugger
From: rogerson
Date: Wed, 06 Mar 1991 12:52
Date: Wed, 06 Mar 1991 12:52
25 lines
1380 bytes
1380 bytes
In article <1991Mar1.215836.21199@cec1.wustl.edu> dave@wucs1.wustl.edu (David T Mitchell III) writes: >For those who don't have BCC, the debugger has one feature that makes the >whole package worth it. A (text-based) dialog box can be set up to log and/or >break on windows messages, ala Spy. It traps messages for window handels >as well as procedures, and they're displayed in a human-readable format (for >example: WM_COMMAND 12 12345). > CodeView for Windows also does this. (page 7-4 of the Tools manual) >So, imagine being able to fire up the debugger and say: > > 1. Log all MOUSE message sent to hMyWindow wwm hMyWindow m > 2. Log all messages sent to WndProc wwm WndProc > 3. Break whenever hMyWindow recieves a WM_LBUTTONDOWN wbm hMyWindow WM_LBUTTONDOWN If you want to capture output to a file redirect CodeView's output with a '>'. -----Dale Rogerson-----
Technical Details
Message-ID:
<303@secola.Columbia.NCR.COM>Path:
arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!peregrine!sceard!ncr-sd!ncrcae!secola!rogersonReferences:
<1991Mar1.215836.21199@cec1.wustl.edu>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!news-server.csri.toronto.edu!rutgers!usc!elroy.jpl.nasa.gov!peregrine!sceard!ncr-sd!ncrcae!secola!rogerson From: rogerson@secola.Columbia.NCR.COM Newsgroups: comp.windows.ms.programmer Subject: Re: Borland C++ Debugger Message-ID: <303@secola.Columbia.NCR.COM> Date: 6 Mar 91 12:52:59 GMT References: <1991Mar1.215836.21199@cec1.wustl.edu> Reply-To: rogerson@secola.Columbia.NCR.COM (PUT YOUR NAME HERE) Organization: NCR NPD Columbia Lines: 25