GrasshopperDeveloperSettings

In older versions of grasshopper, the GrasshopperDeveloperSettings command let you set Grasshopper up so that it could load components from other folders. This was really useful to me since I've written a component to communicate between Grasshopper and my own plug-in which in order to work has to sit in the same folder as the other plug-in but still be loadable by Grasshopper.

I've just downloaded the latest version however and that settings command seems to have disappeared. Have those settings been moved somewhere else or are they now completely unavailable? If the latter, could they be reintroduced? I need them!

Replies to This Discussion

Permalink Reply by Suryansh Chandra on January 13, 2010 at 3:26pm

in version 0.60059, this still in the same place.

Permalink Reply by Paul N Jeffries on January 14, 2010 at 3:05am

You're right - my mistake. Or rather - weirdly - sometimes it's there, sometimes it isn't:

I think probably what's going on is that on the slow-ass computer I'm currently hotdesking on Rhino takes a few minutes chugging away in the background to load all the various plug-in commands, so when I open up Rhino and immediately try to run that command, it hasn't yet been added to the list. Though that doesn't explain why the main grasshopper command is always there (surely Rhino should load all commands from the same plug-in at the same time?). Odd. Looks like I just need to learn a little patience...

Permalink Reply by David Rutten on January 14, 2010 at 4:55am

Hi Paul,

the command should always be there, but usually after a new install Rhino "forgets" all the intrinsic command names and reverts back to just "_Grasshopper". Once you've run this command, all the others should be available in the autocomplete list again.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by Paul N Jeffries on January 21, 2010 at 9:52am

Out of interest, why is this? With most plug-ins (including my own, and for that matter the old version of Grasshopper) Rhino seems to load every command at once. What is it that makes '_Grasshopper' dominant like this? And what's the benefit of doing it this way?

Also, this doesn't appear to be just after a fresh install for me - it's every time I open Rhino. This is a bit annoying since you need to run GrasshopperDeveloperSettings before you've run Grasshopper to load new components, but you need to run Grasshopper before GrasshopperDeveloperSettings will load. (Obviously, you can get round this by unloading grasshopper again so it isn't a massive problem, but it's a little odd.)

Permalink Reply by David Rutten on January 21, 2010 at 11:06am

It's not Grasshopper doing this, it's something in the installer which overwrites the registry. The installer only registers the _Grasshopper command, and probably deletes all the commands Rhino found out about in the past. I'm not 100% sure about this (I'm not the one involved with installers), but I can't think of another cause for this behaviour.

If this happens every time when Rhino starts, it is actually more likely that Rhino is crashing on shut-down. Rhino updates the registry, which includes all the commands it found out about, when it is closed down. If something is crashing in this process before the registry could be updated, these additional commands will never be 'remembered' between sessions.

You may want to flag this up on the main Rhino forum, people like Brian Gillespie and Steve Baer have dealt with issues like these before.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

RSS