Confirm that Plugin Updating is Automatic about rhinocommontemplatepackage HOT 3 CLOSED

AFAIK, 2. is the intended behavior. I defer to @piac as he might know which commit changed this behavior.

from rhinocommontemplatepackage.

Hi @maxsu

I am on vacation but decided to answer your questions quickly. This practice is probably a suggestion due to the command registration policy in Rhino, which @golsby knows more about.

In a few words, if your plug-in loads at startup (not recommended), Rhino will inspect the command names and register them every time, provided that the location of the plug-in does not change. If your plug-in is loaded on demand (default), then command names are cached from the previous command loading. Upon loading, they are updated. This means that the old, changed command names will autocomplete at first, but then might not work when later invoked and finally will be refreshed when the plug-in is finally loaded.

Templates won't do anything regarding this behavior. This is behavior derived from Rhino code.

from rhinocommontemplatepackage.

Sorry I interrupted your vacation!

I confirmed that the mistake was mine: After running the debug build and loading rhino, I 1) tested that the old command did not work - this loaded the plugin and refreshed the cache, so 2) the new command appeared to work. When I skip the first step, the command is unavailable.

This is relevant to the tutorial - loading the plugin is sufficient. Whether this can (or should) be done from the template is defintiely another issue. Thanks for the info!

from rhinocommontemplatepackage.