Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!aplcen!haven!umd5!rossh
From: rossh@umd5.umd.edu (Hollis "The Big Kahuna" Ross)
Newsgroups: comp.windows.ms
Subject: Re: Avoiding the Dreaded AUX Message
Summary: Suggestion.
Keywords: AUX, CodeView, Debugging
Message-ID: <7080@umd5.umd.edu>
Date: 9 Aug 90 23:23:11 GMT
References: <9806@rice-chex.ai.mit.edu>
Reply-To: rossh@umd5.umd.edu (Hollis "The Big Kahuna" Ross)
Followup-To: comp.windows.ms
Distribution: usa
Organization: University of Maryland, College Park
Lines: 19

In article <9806@rice-chex.ai.mit.edu> rpk@wheaties.ai.mit.edu (Robert Krajewski) writes:
>Has anybody figured out a clever way to see if CodeView is running ?
>If one could do so, it would be a lot easier to write debugging
>code that didn't cause such a ruckus....
>-- 
>Robert P. Krajewski
>Internet: rpk@ai.mit.edu ; Lotus: robert_krajewski.lotus@crd.dnet.lotus.com

Assuming that you can't detect codeview, how about a flag, say 
something like: 

BOOL fCodeViewOn 

This is toggle TRUE/FALSE by a menu item.  Then you can use: 

	if (fCodeViewOn) 
		OutputDebugString("Debug Msg");

Hol