Comments on: Debugging RibbonX Invalidate/InvalidateControl failuresâ€¦

By: elias

elias — Thu, 02 Jun 2011 19:27:56 +0000

thanks a lot
i’ve got the same problem
i’ve developed many excel addins in xlam format but i don’t ussually activate any of them at the same time
i change the id of the addins that causes the conflict and the problem was solved

By: Ken Puls

Ken Puls — Mon, 18 Apr 2011 20:32:25 +0000

Hi Will,

Yes, this was a technique that was worked out only a few months ago. But that is exactly what it is intended to do.

By: Will

Will — Mon, 18 Apr 2011 15:19:36 +0000

I recently came across this article which describes a way to “store” the reference to the Ribbon object so that it can be reloaded even after you have a debug, this could solve the question I asked above!
http://www.rondebruin.nl/ribbonstate.htm

By: Ken Puls

Ken Puls — Mon, 04 Jan 2010 16:11:25 +0000

Hi Will,

Unfortunately, no. It’s a very poor implementation, imo, in that there is nothing we can do to keep the RibbonX object alive. One crash and you’re back to reload to reinstitute it.

By: Will

Will — Sat, 02 Jan 2010 13:13:43 +0000

A similar issue related to this one is the following question:

Is there a way to declare the Ribbon UI object as a constant in your VBA rather than using the onLoad routine and a variable?

I want to know this because if the code debugs or if the user resets the VBA project then the reference to the UI object is lost so any Invalidate routines produce a runtime error. This can be quite frustrating, as the only solution (as far as I know?) is to reload the workbook.

Thanks

By: The Ken Puls Blog » Blog Archive » Demonstration of RibbonX add-in conflict dangers

Thu, 18 Jun 2009 15:48:44 +0000

[...] Further to yesterday’s post, I’ve found that the issue with onLoad conflicts is much bigger than I thought. As Bob Phillips pointed out, this isn’t actually a new issue, or one that is strictly an issue with RibbonX, but it is definitely worth mentioning. [...]

By: The Ken Puls Blog » Blog Archive » Ribbon Example Table of Contents

The Ken Puls Blog » Blog Archive » Ribbon Example Table of Contents — Thu, 18 Jun 2009 05:59:04 +0000

[...] Debugging RibbonX Invalidate/InvalidateControl issues [...]

By: Ken Puls

Ken Puls — Thu, 18 Jun 2009 04:27:36 +0000

Looks like that might be a very good idea, Bob. I just found out today that this issue is even bigger than the onLoad routine… it’s any conflicting add-in. Not good.

By: Bob Phillips

Bob Phillips — Wed, 17 Jun 2009 22:01:19 +0000

This is a particuarly nasty problem Ken in that something just doesn’t work, but this is not a new issue, nor ribbon specific. I recall that when Frank Kabel and I wrote QDE a call to the help invoked some other help file. The problem was that we called the procedure ShowHelp as did the other addin (I am pretty sure it was one of Rob Bovey’s, I recall writing to him to check that he used that name). We were lucky becuse we got a very visual response, even if odd. Since then I have always used the App Id in the procedure name for the help invocation. I will just take your advice and use it in your callbacks as well.