![Customize Customize](/uploads/1/2/5/4/125445159/778362344.png)
By Peter Weverka. In Microsoft Word 2016, you can change the keyboard shortcuts. A keyboard shortcut is a combination of keys that you press to give a command. For example, pressing Ctrl+P opens the Print window; pressing Ctrl+S gives the Save command.
I have a plugin for Word. On office for windows it is able to show a customised ribbon using ribbon XML. On office 2011 for mac, it ignores this ribbon but I am able to add a CommandBar (A dropdown menu at the top). These allow me to create a menu system for my various macros. In Office 2016, when I try to create a commandbar I get the error: 'Method 'Add' of Object 'CommandBarControls' failed. It also does not allow custom ribbons, it doesn't pick up the XML which is in the dotm file (Neither does it seem to let me manually change the ribbon).
This leads me to the question - Is there any way, any way at all, that I can add some buttons somewhere to fire macros on this version of office? Preferably something I can create using VBA (Currently the commandbars are added from VBA). Since this works in Office for Windows (preview) as well as old versions of office for windows, as well as Office 2011 for mac - why wouldn't this work here? Create a new.dotm file in Word 2011, run the CreateCommandBar macro and then copy the toolbar (using the organizer dialog) and SubItworks macro to the.dotm file. Put the.dotm file in Word 2016's startup folder and you'll see the toolbar in the ribbon's Add-in tab. It's buggy though - the only controls that seems to work are top level buttons. Clicking on the popup button doesn't display a menu, and even the top level buttons aren't drawing properly when you click on them.
I've had better luck manually creating a new toolbar in Word 2011 (View:Toolbars:Customize Toolbars and Menus) and then creating buttons by dragging macros to the toolbar. You can also manually set button properties using Visual Basic's locals window once you get a reference to the toolbar. Buttons created that way seem to behave properly as long as you don't change any button properties at runtime.
I think this is actually the answer, unfortunately. I never knew Microsoft Office was such a mess, it's only recently i've had to work with it. No VBA in office 2008, acceptable VBA support in 2011, then a horrible lack of support in 2016. It's annoying that it's not even consistent across different applications within the same version of office, nevermind different versions or different operating systems.
I don't think we can use.NET either, which leaves anyone wanting to develop add-ins for any mac version other than 2011 in a fairly poor position. Even on windows it's always compromising.
– Jul 15 '15 at 11:26.