Search code examples
excelribbonxvba

Custom UI Editor flakiness

I have been using the above tool and Excel 2013 with mixed success. The good news is that it eventually works, the bad being that when it doesn't the following horrible things happen when modifications inside of the Editor are made:

  1. modules with callback code revert to their state before the callbacks were added (ie, the code is lost!). This seems to happen even when there are no errors. This is frustrating!
  2. custom tabs and context menus just don't show up if there is a conflict. For example specifying a callback to getLabel in xaml when there is also a label attribute specified. Of course this is my bad but it wouldn't hurt if the tool would catch this for me.

Question Is the Editor the state of the art for customizing the ribbon and adding context menus. I realize the price is right but would gladly pay for a smoother and more reliable dev experience

Solution

  • The CustomUI editor doesn't affect modules in the workbook - but if you do make changes to the workbook while it's opened in the UI editor, then yes you may lose changes.

    Also, you can set Excel to warn you of UI errors which will at least assist you in working out why your tabs/controls aren't appearing.