Please make “Preparing Plug-ins for First Use” smarter and optional !
from a user perspective:
Please:
An initial dialog - Do you want to load plugins from old rhino installations.
if yes - Allow users to select Plug-ins that should be loaded or not:
skip all
load all
load selected
from a developer perspective
rhino
I think the behaviour of “Preparing Plug-ins for First Use” must be very solid. (currently 31. July 2025) it is not)
This means, there should be a time-out mechanism if a plugin does not load, and the dialog should accept a ESC/Cancel.
Even if a plug-in stuck in un accessible dialog / commandline input or something else.
i am running into the same issue as described here:
sdk / rhinocommon
custom plugins should have a mechanism to only load on the rhino version they where compiled against / developed with.
Or have a property/function that returns the support RhinoVersion(s)
Or have a property that tells Rhino not to Auto-Load/Transfer on new installs / new Versions on the same machine.
I imagine that the plugin-class could have a very restrictive default implementation
public virtual bool AllowAutomaticFirstUseNewInstallations { get; set; } = false;
workaround ?
how can i stop “Preparing Plug-ins for First Use” ?
I have a few custom plugins that use an interactive licence mechanism “OnLoad”.
I do not want to mess up my Rhino 8 installation to be able to start testing WIP.
Start in safe mode failed ! on a fresh installation
thanks for some update regarding this.
tom