Without further ado:
<group idMso=“GroupClipboard” visible=“false” />
I’m finally working my way through this book:
OK, so here’s my initial impressions. Initial, mind you. I do a tiny bit of xml coding and I’m able to disable the cut-copy-paste triumvirate without VBA. In addition, the Ribbon changes based on the active workbook. When my template is active, the Clipboard group disappears. When I activate a different workbook, it comes back. This is good. I can eliminate half of my Windows_Activate and Windows_Deactivate events because the “toolbars” take care of themselves. I’m sure I’m missing something, but this seems like quite an improvement to me.
But it’s not all puppies and kittens. Ideally I’d like to just disable the controls rather than hide the whole group. My problem is that I don’t know the idMso attribute for the controls. I found this list of control IDs but I haven’t downloaded it yet.
As a developer (not a user), my first impression of the Ribbon is a good one. I fully expect it to turn sour and that’s where you come in. For instance, I hear that it’s nearly impossible to truly disable everything Ribbon. I don’t create dictator apps, so I’m not sure how this is going to effect me. Yet, I know it will somehow. If you have a particular gripe about the Ribbon, from a developer’s perspective, I’d like to hear it. It will help me prepare for the inevitable.