Some fixes in capabilities

[Tony Lambregts]

Eric Pouech wrote:

>>While I am on the subject: as I mentioned in my other mail on this
>>subject. Turning on gdi in winedbg (or any other channel/api that the
>>debugger uses) will include calls from winedebug as well as the program
>>I am debugging. This is an unhelpfull situation.
>>    
>>
>are you sure of this ? debug channels are only changed in the debugged
>app, not in the debugger
>aren't you looking at different threads ?
>
>
>  
>
My appologies. (I am a VERY thick at times) I think most of my problems 
with this is that I am/was doing it (The Wrong Way) (C) OK. I think I 
should clarify since I brought it up  There are two ways of getting 
extraneous messages from winedbg in the log.

1). Starting winedbg with --debugmsg +(any channel you want a trace of) 
ie: +loaddll

2). Any fixme message will get into the log regardless of whether it is 
generated trough the app or winedbg. I would assume this also applies to 
err and warn as well but I have not tested them

I think that now that I know about these two conditions (and avoid them) 
I should be able to get a good clean log.


-- 

Tony Lambregts