Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!rice!uw-beaver!cornell!rochester!udel!wuarchive!cec2!news
From: dave@wucs1.wustl.edu (David T Mitchell III)
Newsgroups: comp.windows.ms.programmer
Subject: Borland C++ Debugger
Message-ID: <1991Mar1.215836.21199@cec1.wustl.edu>
Date: 1 Mar 91 21:58:36 GMT
Sender: Dave Mitchell
Organization: Washington University, St. Louis MO
Lines: 18

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.

dave	dave@wucs1.wustl.edu
	the mira corporation
	314/434/4343