Change built-in groups in the Ribbon

Hi all

It is not possible to add to or remove controls from built-in groups in the Ribbon. For example, the
Format Painter button from the Home tab’s Clipboard group cannot be removed from this group.

But there is a way around this restriction.
We can hide a built-in group and then duplicate it with RibbonX.
And then we can modify our duplicate group anyway we want.

You can find all the information you need on this new page on my site.
http://www.rondebruin.nl/xmlribbongroups.htm

Let me know if you have problems or have suggestions.

Ron de Bruin
http://www.rondebruin.nl/tips.htm

9 Comments

  1. jkpieterse says:

    Good stuff Ron!

  2. This is such a rockin idea Ron. Fantastic work!

  3. sam says:

    Hi Ron,
    Nice Article,
    What is the addins Tab called

    Sam

  4. Ron de Bruin says:

    Hi Sam

    I will add this name also to the page this weekend
    Example to add a group in this tab with a custom button from my QAT add-in

  5. Ron de Bruin says:

    I see I can’t add RibbonX to this comment

    The name is TabAddIns

  6. Just PLEASE nobody consider doing that in an addin and releasing it! We’d end up with lots of copies of the group, all with just a single button different.

  7. Ron de Bruin says:

    I agree with you about add-ins Stephen.
    For Add-ins add a custom group in a built-in tab or on a new tab.

    But for workbooks it can be useful

  8. I agree with Stephen 100% here. I would even be cautious with a visible workbook. I think that a workbook that has RibbonX associated with it should probably have its own tab.

    Adding a new group to a tab would be my next choice, but replacing a group with your own could be trouble for other add-ins expecting a standard setup. (The add-in could no longer hook its functionality to built-in controls which have been hidden and then replaced with clones.)

    I think that this is fine to get around the customization restrictions for one’s own use (I do a lot of this for my own Ribbon setup), but I would never do this for an add-in that I made for others.

Leave a Reply