No, I think - tatic BYTE params = VTS_BSTR VTS_I4 VTS_VARIANT VTS_VARIANT; is correct because I have seen this in http://repositorium.googlecode.com/svn/trunk/AbstractSpoon/OutlookImpExp/Source/msoutl.cpp
I would hazard a guess from the code that its the same issue you had before, regarding the passing of [in, optional] VARIANT parameters. Everytime you come across an [in, optional] VARIANT parameter, what you have to pass is the address of a VARAIANT that contains type VT_ERROR, and value DISP_E_PARAMNOTFOUND. In this case, from the static BYTE params declaration there are two "optional" parameters.
I have not looked up what dispatch method 0x66 is so I am not 100% sure.
The presence of a VTS_VARIANT in the params array does not always mean optional, however an optional parameter is always a variant.
The VTS_BSTR in the params array of an InvokeHelper call is expected to be an LPCTSTR. to allow the CString to pass the correct value always type cast it to (LPCTSTR). The type casting is neccessary because InvokeHelper is declared as void AFX_CDECL InvokeHelper(DISPID dwDispID, WORD wFlags, VARTYPE vtRet, void* pvRet, const BYTE* pbParamInfo, ...); so the compiler doesnt know specifically what to pass. By type casting it you ensure the correct value is passed.
I have tried your suggestion and that did work! However, because one of parameters is a bool what is the correct syntax for passing a bool? Would it be COleVariantBool varOptionalBool (VT_TRUE, VT_ERROR); ?
Further, when the line for saving the properties is called InvokeHelper(0xf048, DISPATCH_METHOD, VT_EMPTY, NULL, NULL);
It gives an unhandled exception again. Looking at the MS Office VBA for this, properties don't save method, and it appears to me that when you add and set the properties this carries out the saving. Have I got this wrong? Is there something else I need to do?
I am unsure why Save (0xf048) would cause an exception. What is the exception ?
I am also unsure why you dont use type-safe methods of invoking Outlook. Open the Class Wizard dialog "key combination Ctrl+W". Click "Add Class...". Click "From a type library...". Locate your MSOUTLxx.OLB, mine is in "C:\Program Files\Microsoft Office\Office12" click Open. Select the appropriate classes, or all of them, and click OK. This will add to your project header and implementation files that, in my humble opinion, will make your life easier.
OK. Thanks. So far so good, but the function PdhAddCounter needs localized strings, thus in Germany you need german strings, in france you need french strings, etc. Damn, I'm not that language professional and the recently added function PdhAddEnglishCounter is not available on XP systems... ( I love those guys in Redmond...).
Is there a way to find out the localized corresponding language strings?
I am trying to develop IE toolbar in MFC using COM. On win7, the required dll (i.e. SelectorObjectAPI.dll) is present in %program files%\Microsoft\Internet Explorer Developer Toolbar\. But I am it is not there in XP SP3. I reinstalled IE 8 and result was same. Both m/c has IE 08.
So if Developer Toolbar is not an option, what else can I do. I need to create a toolbar for IE in C++ (specifically MFC + COM)
I have come across some samples but those samples need their (ready made) helper code to be included.
It's is learning adventure for me, so I would like to do every thing myself... Looking for any tutorial.
I create an owner draw btn with the styles WS_VISIBLE | WS_CHILD | BS_OWNERDRAW, and I try to use WM_DRAWITEM to deal with different button actions:
if lpDrawItemStruct->itemAction == ODA_DRAWENTIRE, I Draw a normal state button picture, when mouse clicks on the button, I draw a sink style picture. but the wm_drawitem message seems not responsible for mouse hover action. Someone could give a solution?