I am getting back to Rhino plugins for Mac.
I am doing a little bit more investigations on this issue with .plist file.
First, I don’t find any of my plugin info in the plist that I exported from Rhino by “ExportPreferences”. However, when I use an online plist decoder tool to convert the original
com.mcneel.rhinoceros.plist, I found the plugin path is still there:
and I searched the plugin’s GUID, I found these data related to plugin scattered in this plist file.
So my guess is, when Rhino loads this
com.mcneel.rhinoceros.plist file, it doesn’t check if any plugin has been removed from original location, and then remove the pluginRegistry from this plist. Or Rhino does all above steps, and just doesn’t save the new plist. @dan please let me know if you need anything from me to recreate the issue.
To me, this
com.mcneel.rhinoceros.plist is similar to Windows’ Registry.
On Windows, we can register plugin by adding it’s path to
HKEY_LOCAL_MACHINE\SOFTWARE\McNeel\Rhinoceros\6.0\Plug-Ins\F3CF4A28-EA9E-4E08-BABA-5FC6645A5D72 , and Rhino on Windows will check this path when it loads.
Remove plugin from the original path, Rhino will update this registry next time it is trying to load, and remove it from registry if it cannot find rhp. Or we can remove the plugin directly from registry, which de-links the rhino and plugin.
So on Mac, guess Rhino does the similar thing to plist. What’s the best process to register a plugin, is saved somewhere else instead of ~/Library/Application Support/McNeel/Rhinoceros/MacPlugIns/, to plist?
To give you some background that why I want to register plugin to plist directly on Mac: we are building an installer to install our rhino and grasshopper plugin along with all required simulation engines and libraries, I need the rhino plugin registered/unregistered within this installer/uninstaller.
Thanks again for your helps,