I am re-posting this question because further work has shown that the original post title was not accurate, and the post had ground to a halt.
The problem is that our plugin, which is derived from a rhino 5 commons plugin, loads ok but is treated as disabled on the next rhino launch.
We normally install plugins for Rhino 4, 5 and now 6 programmatically, but the same problem occurs during a hand install, so I will show the steps for that:
Just out of curiosity, are you able to make changes in Tools > Options? Try for instance changing the viewport background color. I’d like to know if the change sticks after you close the Options dialog.
Hi Andrew,
I’ve tried the steps that you laid out and still haven’t been able to repeat the problem.
Try the following;
open regedit and go to HKCU\Software\McNeel\Rhinoceros\6.0\Global Options\Plug-ins
you should see an entry for 112f133a-8afd-4656-b04a-d313a05800e5 which is your plug-in’s ID
delete this entry; it is what sets the “disabled” flag for your plug-in
also go to HKCU\Software\McNeel\Rhinoceros\6.0\Plug-ins and find the 112f133a-8afd-4656-b04a-d313a05800e5 key. This is the key that holds all of the cached information about your plug-in. Delete this key too.
Start Rhino and repeat the steps that you laid out for manually installing. Do you still see the bug that you are describing? I’m curious in case the Global Options flag got set at some point in time and we’re just dealing with stale cached information in the registry.