why GetCustomUI is not called (COM C++)

[Shang Yu]

Hi guys,

I'm prototyping a COM(C++) addon for Excel, I implemented the IDTExtensibility2 and IRibbonExtensibility interface on my component. IDTExtensibility2 works fine but IRibbonExtensibility does not, that is, GetCustomUI never get called. 

I know this is the group for Excel-DNA. But I believe underlying mechanism is similar. So, any suggestion? Many thanks!

[1585471449]

您的邮件已收到，谢谢！

[Govert van Drimmelen]

There's nothing unusual about the IRibbonExtensibilty COM interface or how Excel calls it, as far as I know. Depending on how you are implementing the COM interfaces in C++ you might need to add the interface to some ATL map or similar, and check that the interface GUID is right etc. I expect that Excel calls QueryInterface to get to it in the normal COM way.

-Govert

--
You received this message because you are subscribed to the Google Groups "Excel-DNA" group.
To unsubscribe from this group and stop receiving emails from it, send an email to exceldna+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/a0c7a653-dc92-41c6-abaa-cc9f5094a041n%40googlegroups.com.

[1585471449]

您的邮件已收到，谢谢！

[Shang Yu]

I can confirm that Excel has queried the IRibbonExtensibility interface and the querying is succeeded. It seems that Excel just query the interface and hold it for later use. So, I wonder if there are some prerequisites for calling GetCustomUI? Following is part of my ATL class for reference. Many thanks!

...

struct ATL_NO_VTABLE CAddon :
  CComObjectRoot,
  CComCoClass<CAddon,&CLSID_CAddon>,
  IRibbonExtensibility,
  ICustomTaskPaneConsumer,
  _IDTExtensibility2 {
  DECLARE_REGISTRY(CLSID_CAddon,"ebi.comaddon.1","ebi.comaddon","office",THREADFLAGS_BOTH);
  DECLARE_CLASSFACTORY();
  BEGIN_COM_MAP(CAddon)
    COM_INTERFACE_ENTRY(IRibbonExtensibility)
    COM_INTERFACE_ENTRY(ICustomTaskPaneConsumer)
    COM_INTERFACE_ENTRY(_IDTExtensibility2)
  END_COM_MAP();

...

};

[Govert van Drimmelen]

I'm pretty sure you need IDispatch support in there - inherit from IDispatchImpl too, add IDispatch to the interface map etc. The ribbon callbacks declared in the XML will be called via IDispatch, so Excel might be checking for that even before calling you GetCustomUI.

-Govert

To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/ef1df843-6b4b-4594-8dba-a9150b282e27n%40googlegroups.com.

[Shang Yu]

Thank you. It works roughly this way

...

struct ATL_NO_VTABLE CAddon :
  CComObjectRoot,
  CComCoClass<CAddon,&CLSID_CAddon>,

  IDispatch,

  IRibbonExtensibility,
  ICustomTaskPaneConsumer,
  _IDTExtensibility2 {
  DECLARE_REGISTRY(CLSID_CAddon,"ebi.comaddon.1","ebi.comaddon","office",THREADFLAGS_BOTH);
  DECLARE_CLASSFACTORY();
  BEGIN_COM_MAP(CAddon)

    COM_INTERFACE_ENTRY(IDispatch)
    COM_INTERFACE_ENTRY(IRibbonExtensibility)
    COM_INTERFACE_ENTRY(ICustomTaskPaneConsumer)
    COM_INTERFACE_ENTRY(_IDTExtensibility2)
  END_COM_MAP();

...

};

[Govert van Drimmelen]

Wonderful. You might need to inherit from IDispatchImpl and not just IDispatch for the callback implementations to get hooked up , but I'm not sure.

-Govert

To view this discussion on the web visit https://groups.google.com/d/msgid/exceldna/f6521a1f-fd38-4e6a-808a-3ba24c002e4fn%40googlegroups.com.