Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!jpl-devvax!huey!brad
From: brad@huey.Jpl.Nasa.GOV (Brad Hines)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Borland C++ Debugger
Message-ID: <11712@jpl-devvax.JPL.NASA.GOV>
Date: 7 Mar 91 03:42:37 GMT
References: <1991Mar1.215836.21199@cec1.wustl.edu>
Sender: news@jpl-devvax.JPL.NASA.GOV
Reply-To: brad@huey.Jpl.Nasa.GOV
Organization: JPL Spatial Interferometry Group
Lines: 24

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).

So, imagine being able to fire up the debugger and say:

	1.  Log all MOUSE message sent to hMyWindow
	2.  Log all messages sent to WndProc
	3.  Break whenever hMyWindow recieves a WM_LBUTTONDOWN


Nice!  Much better than trying to run Spy to figure out what's going on.

------------------------------------------------------------------------

I like Borland, too, but Codeview has done this all along...

-- 
Brad Hines
Internet: brad@huey.jpl.nasa.gov
Jet Propulsion Lab, Pasadena, California