New rui not loaded after plugin update

Hello

I distribute a collection of several plugins and a toolbar for use of the technicians in our company. The Plugin contains 2 rhp files (one containing plugins we wrote in c# and one containing our vb script plugins) and a rui file.
We have always had big problems updating the rui file when adding new commands in rhino 7. New RUIs just were always ignored, if a RUI with the same name already existed in the users "AppData\Roaming\McNeel\Rhinoceros\7.0\UI\Plug-ins" folder.

I was hoping this would automatically be solved with Rhino 8, as the RUIs now stay in the "AppData\Roaming\McNeel\Rhinoceros\packages\8.0" folder and are loaded from there. However when I made a new YAK this morning with a new macro, button and menu in the RUI, the toolbar refused to update again.
When I check the properties in tools->options->toolbars I can also confirm, the toolbar is still from version 1.0.4 of our plugin, although I updated to 1.0.5 via package manager and the new RUI also can be found in the package folder of version 1.0.5. I even ran the “reset” command and “deleted toolbar customizations” before installing the update 1.0.5.

The RUI loads correctly if I first uninstall the old version, but even then it stays hidden. I always have to go to tools->options->toolbars, select it in the dropdown menu and place the check mark for it to show up

How can I make sure new toolbars are always correctly loaded and shown with new updated plugin packages?

Any hint would be appreciated a lot, as I have been running around in circles for weeks now trying to solve this problem.

Thanks in advance!

I logged this as https://mcneel.myjetbrains.com/youtrack/issue/RH-84576/YAK-package-fails-to-update-RUI-file

Thanks @brian this has been a total pita since I started development of Rhino plugins/YAK files.

It makes no sense AT ALL that .rui files are never updated with the plugin.

It would be the expected behavior that if a YAK file contains a new .rui file that the older version would be updated/replaced.

Cheers

DK

1 Like

RH-84576 is fixed in Rhino 8 Service Release 15 Release Candidate