Ribbon Extensibility: A VBA Sample

Jensen Harris An Office User Interface Blog Ribbon Extensibility A | Insomnia Cure

Sat, 13 Jun 2009 09:43:27 GMT

PingBack from http://insomniacuresite.info/story.php?id=194

The Office 2007 UI Bible | MS Tech News

The Office 2007 UI Bible | MS Tech News — Tue, 28 Oct 2008 01:39:05 GMT

PingBack from http://mstechnews.info/2008/10/the-office-2007-ui-bible/

The PODA Blog - News, views and articles from our membership » Programming/Customizing the Excel 2007 Ribbon Using VBA

Wed, 21 Mar 2007 01:10:00 GMT

PingBack from http://proofficedev.com/blog/2007/03/20/programmingcustomizing-the-excel-2007-ribbon-using-vba/

re: Ribbon Extensibility: A VBA Sample

Patrick Schmid — Tue, 25 Jul 2006 10:45:31 GMT

Tim: Unfortunately, you can't. Excel developers have reverted to using a combination of an Excel 97-2003 file with an Excel 2007 add-in for the RibbonX to make one add-in for all Excel versions.

re: Ribbon Extensibility: A VBA Sample

Tim Teichman — Tue, 25 Jul 2006 07:48:27 GMT

Based on reading the posts, I don't think this example helps me at all. I develop an XLT that is distributed to about 300,000 users, and I don't know what version of Excel they have. They don't know either, probably.

I need one XLT file that will work with all the versions of Excel and that will add a UI as applicable, by excel version. How does one modify the ribbon using **just** VBA as we could modify the menus and toolbars before?

re: Ribbon Extensibility: A VBA Sample

Patrick Schmid — Sun, 18 Jun 2006 05:10:26 GMT

keepITcool: bug. Thanks for your email. I bugged it
Btw, you should try the custom UI editor tool Savraj posted a link to in the post above. It makes one's life of editing RibbonX with an Office document/template a lot easier.

re: Ribbon Extensibility: A VBA Sample

keepITcool — Thu, 15 Jun 2006 14:53:11 GMT

Designflaw or bug?

I found that for VBA the callbacks in the XML must be fully qualified. e.g. getEnabled="testbook.xlsm!cbGetEnabled"

Otherwise when switching documents/worksbooks
(with the custom tab visible) several errors are generated like:
"Cannot run the macro "cbGetEnabled". The macro may not be available in this workbook or all macros may be disabled."

Is there a simple means to specify my container name via a constant or function in XML or do I need to: unzip, search & replace,rezip. when I simply rename my workbook?

re: Ribbon Extensibility: A VBA Sample

keepITcool — Sun, 11 Jun 2006 13:02:31 GMT

Invalidate was the trick!

However: i think i've got a bug:
GetLabel of a Button in SplitButton container. gets called onLoad but doesn't get called on Invalidate. GetImageMso does.

For clarity: I'm figuring out how to make a multilanguage ribbon. User makes language selection and ribbon must relabel to chosen language.

re: Ribbon Extensibility: A VBA Sample

Patrick Schmid — Sun, 11 Jun 2006 12:04:04 GMT

Take a look at my blog: http://pschmid.net
It has a lengthy discussion of what you should do to follow the Office UI guidelines. I also discuss all the things you can do, even those not mentioned in the Microsoft documentation ;)
Invalidate simply tells Office that a particular control, tab or group is no longer valid in the UI meaning that it should call all "get" callbacks of it again to get its new status.

re: Ribbon Extensibility: A VBA Sample

keepITcool — Sun, 11 Jun 2006 11:33:56 GMT

Patrick.
I'm exploring the functionality of the Ribbon from a developer pov. I found important things I could but can't and some I can but couldn't.

I'd missed the purpose of the .Invalidate method. It may be what the docter ordered. Curious name though.

"Neither should you" has got me worried.
I'm still finding out if I can if I want to.