NewInspector event causes debug assertion in Outlook 2003

[optimist]

and I can't see what's wrong. The assertion is on line 4103 of atlcom.h and
is:
"m_dwEventCookie == 0xFEFEFEFE" and appears each time a NewInspector event
should get fired (but doesn't). I noticed that if I changed my ATL_FUNC_INFO
parameter to the SINK_ENTRY_INFO() call from

_ATL_FUNC_INFO OnSimpleEventInfo ={CC_STDCALL,VT_EMPTY,0};

to

_ATL_FUNC_INFO OnNewInspectorInfo ={CC_STDCALL,VT_EMPTY,1,{VT_DISPATCH}};

That it changed the debug assertion to the one above, from

"pdispparams->cArgs == (UINT)info.nParams" on line 4048 of atlcom.h.

But that was just copying someone else's code, which is mostly what I've
been doing all through this project...

Any pointers are much appreciated.

 

[optimist]

I'm making some progress, but could use some pointers on how to sink close
events in a NewInspector callback. Right now it works fine for the first
NewInspector call, but each succeeding call gets the assertion. I see that I
need to dynamically allocate a new sink for each OnNewInspector() where I
want to sink Close() events, but am not sure how to do that.

Also, how do you unadvise in a Close() where you don't know which object is
being closed?

J

 

[Ken Slovak - [MVP - Outlook]]

I don't recall any Inspector wrappers, which is what you need, in C++ but
maybe an example in C# might help:
http://www.outlookcode.com/codedetail.aspx?id=797