Grasshopper

algorithmic modeling for Rhino

Totally Confused About Location of Third Party Components in Rhino

Please can some one clarify why where and when a third party .gha component should be copied to

 

a) to the comonents folder listed in the grasshopper menu bar for File > Special Folders > Components Folder

b) copied to the folder C:\Program Files (x86)\Rhinoceros 4.0\Plug-ins\Grasshopper\Components

 

I have noticed that for some components it doenst work if I copy it to a) but will work if I copy it to b) and vice versa.

Is it because some legacy components no longer follow rule a). I presume both Rhino 5 and Rhino 4 can access the same componentsin a)

 

What is the future protocol for this?

 

cheers

 

Views: 500

Replies to This Discussion

Hi Steve!

DR can correct me, but I think the intent is default (standard?) .gha's live in the plug-in directory while add-ons (third party) live in the special folder.

The components in the plug-in directory are over-written with every new GH installation so the special folder was created as a "safe" place to keep track of add-ons.

p.s. if you drag and drop a .gha to the canvas it puts a copy in the special folder.

nice, thanks.

 

So can you tell me what are user objects? I think these are just clusters saved to the user objects folder right? How do i save these

 

P.S. good to hear from you, hope things are well for you at the mother ship

hmm...  you're right.  

A .ghuser is a non-scripted component from a cluster.  I think you can wrap it up into a .gha if you want to...

Members have produced some guidance docs (which are now a bit old) but might be helpful for general info.  I've reattached them.

p.s. for the longest time I didn't realize Steve Lewis was you until I looked at your pic more closely!  hope your new mother ship is sailing along smoothly too.

Attachments:

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service