Hi McNeel peeps,
I’m getting frustrated over the many places you are searching for plugins and how cumbersome it is to get an overview.
Trying to share the (known to me) places that I have gotten plugins installed from:
%appdata%\McNeel\Rhinoceros\X.0\Plug-ins%appdata%\McNeel\Rhinoceros\packages\X.0%programfiles%\Rhino X\Plug-ins%programdata%\McNeel\Rhinoceros\X.0\Plug-ins%programdata%\McNeel\Rhinoceros\packages\X.0
- all other drag-and-drop locations from where you dragged .rhp files.
In the Rhino Options I can’t really remove a plugin, I can only disable it (which renders Blocking XX plugin on startup in the console).
If I have to remove it from Rhino Options, I need to open plugin properties, copy the registry path and remove that entry from the registry. A very manual process. And just when you think you removed it, it will auto install if its in any of the magical folders above.
I would ask for a remove button in the Plug-ins screen that would have different actions depending on the source of the plugin:
- Remove from registry if the rhp is free floating in a random folder
- Remove from one of the default folders if thats the case so it doesnt autoinstall
- Remove through packageManager if it exists here
Feel like its a bit the wild wild west when it comes to combining PackageManager with non-PackageManager 
2 Likes
Hey @sonderskovmathias ,
To summarise, you would like us to add an uninstall option to the right click menu inside the PluginManager window?
I mocked it up in paint just to clarify
– cs
3 Likes
Yes that’d be lovely, even though the plugins could have various origins.
Keeping all the paths here for reference if anyone else I looking
It would indeed be quite lovely, (I had also always wanted this). As I started creating the YouTrack I stumbled across many other users asking for this, and lots of discussions around it.
Why hasn’t this been done already? It boils down to a few reasons currently. And these reasons are also why it’s unlikely to be added.
- Yaks can be uninstalled via the Package Manager, and plugins should use yak going forwards
- If a Plugin has its own installer, it should perform it’s own uninstall
- If a plugin was installed through a different system, we can’t know what other files it installed and we can’t perform a total uninstall
1 Like
In that case try providing a small info box on that uninstall button.
ons. 19. jun. 2024 22.06 skrev Callum Sykes via McNeel Forum <notifications@mcneel.discoursemail.com>:
What would the info box tell the user?
On top of my head something like…
If in a random folder;
"Looks like this plugin was drag-n-dropped or installed via external installer.
If it’s installed via an external installer we recommend running that uninstaller to remove it completely.
Click here to open the folder or click here to unlink it (removes in registry)"
If it’s a standard mcneel plugin warn about that also. But some people would like to clean up (I don’t have a 3dconnexion mouse for instance)
If it’s in one of the default search folders:
“Looks like this plugin was installed via an external installer. As it is placed in a default folder you’ll have to remove the file or block it here.”
Just for transparency
