Grasshopper

algorithmic modeling for Rhino

So I have just tried out the "Export & Reference" functionality of Grasshopper. Besides it not working on a file server, once again rendering GH unusable for several minutes before working just fine, it resets the Clusters Name, Description, Icon and shortened input names.

The exported cluster:

The exported cluster dropped into a new file:

Maybe I am doing something wrong, but I have not found a way to place a .ghcluster into a document other than dragging it in from the Explorer. Surely there must be another way!?

How can we retain the information in Name, Description, Icon and inputs with a referenced file?

Views: 807

Replies to This Discussion

Hey,
U ever tried to create an 'UserObject' ?
select the cluster and go to 'file->Create User Object...'
There u can give a name, description, category, subcategory, icon, and so on....

Greets
mark

Hi Mark.

I have and am using it a lot. The obvious difference is, that you can't update the User Object retrospectively, can you? And a lot of times it doesn't make sense to create a user object, but I might still want to use a cluster elsewhere, but keep it referenced. I see user objects as small pieces, but "Export & Reference" for larger things. Also user objects are hidden in the roaming folder somewhere, whereas referenced files can be placed anywhere and therefore shared along with the regular .gh file.

Otherwise I don't understand what the point of "Export & Reference" is. And surely it should retain the name, description, etc. That seems like a bug to me!?

Hi,

Just came across this annoying problem and stumbled upon this thread.

It seems to me like a bug and User Object does not replace the convenience of saving clusters to locations outside of Windows' user folders.

If only McNeel would iterate quickly and fix some of these bugs that have been around for years it would be great.

RSS

About

Translate

Search

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service