Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!sun-barr!newstop!jethro!Sun.COM!yaturner
From: yaturner@Sun.COM (James Turner)
Newsgroups: comp.windows.ms.programmer
Subject: Re: Codeview (CVW) in window?
Message-ID: <3740@jethro.Corp.Sun.COM>
Date: 2 Apr 91 21:05:34 GMT
References: <7850001@pollux.svale.hp.com> <149000015@eriador>
Sender: news@jethro.Corp.Sun.COM
Reply-To: yaturner@Sun.COM (James Turner)
Organization: The Houses of the Holy
Lines: 31

In article <149000015@eriador>, mguyott@eriador.prime.com writes:
|> 
|> A company called Nu-Mega Technologies, P.O. Box 7607, Nashua, NH 03060-7607
|> has the product you are looking for.  I am not sure what it is called though.
|> They advertise that it will allow you to run CVW in a window under Windows.
|> It probably requires a 386 and protected mode.  But you should call them and
|> find out.  They can be reached at (603) 888-2386.
|> ----
|> Two of the worst things we teach our children are that a knowledge of science
|> is nice but not necessary, and a knowledge of sex is necessary but not nice.
|> 

I think that I am some what unclear on the subject or I have not followed
the thread of this topic. If CVW is running on the same display as the 
window that you are debugging:

1. the simple act of moving the cursor from your window (the debuggee) to
the debugger window will generate unwanted events 

2. if your application dies ungracefully and hangs windows or just freezes
the pointer how will you get a postmortum from the debugger

3. if you want to debug a modal dialog box etc.

you get the idea or am I missing the obvious ???

-- 

Mencsh tract und Gott lacht

yaturner@corp.Sun.COM