deleting an component in mac rhino / gh2 leaves the geometry preview behind in the viewport until I orbit or otherwise cause it to refresh
opening preferences throws an exception
and switching to another app leaves component dropdown in front of EVERYTHING:
How do you do the exporting? the red “arrow” button over the icon in the GH Icon panel doesn’t seem to do anything for me — but maybe I’m looking in the wrong place.
Like said by David, it is just the first number.
You’ll have to type n+59
To see the function, use a Preset Picker and see the output in a panel.
Oh! Thanks!
Are attribute user texts (i.e., keys:values) possible types of metadata?
I’m not seeing a way to reference/filter objects by user text values, and I wasn’t sure if those are completely different from metadata, just not implemented in a component yet, or TBD by a future plugin developer.
1 Like
great! thanks
but i doesn’t find Custom Preview component for Displaying(Brep Mesh Curve…)?
and Intersect Tab (region union …brep curve …)
in this Version gh2?
is it True?
How I could find and open the panel to produce GH icon as you mentioned above?
find it,THX!
As a seasoned Grasshopper user, it’s scary how many things in terms of nomenclature have changed.
If you used to like working with named components instead of icons, you’ll be disappointed that you currently can’t get rid of the icons, in favour of an abbreviated text description.
Also the names that can get displayed in bubbles above the components seem design-wise kind of half-arsed, compared to the rest, a worse version of what plug-ins like Sunglasses currently try to do.
Most icons are nicely designed, however they are by nature simply less readable than a short text, at least for me. I wonder what all these soft pastell colours mean for people with impaired vision, colour blindness, and such.
Now that the icons scale while zooming out, big definitions will probably look like a bowl of skittles.
Honestly, I don’t about this.
The little sparkle animation when connecting to an input is cute, however it’s probably going to get old quickly.
I wonder what all the little animations and effects mean for canvas performance, something that GH1 still struggles with at least on macOS, and without all the eye candy.
Having a dedicated buttons to turn off component activity or visibility is nice, however why are they so huge?
Why is a stylised Batman Beyond on the icon for the randomize trinket?
Also the Vornoi component should be in every version, even an alpha.
1 Like
Mostly not implemented yet. The hard part of meta-data was making sure all data could be tagged, all the dozens of functions that will use the meta-data to do things have yet to be written. Only display and baking at the moment are sort of hooked up.
Meta-data is a collection of named values, very much like user texts in Rhino. However, Grasshopper puts stringent limitations on what type of data is stored in meta data. Only immutable data is allowed, as it is my assumption that meta data is probably shared amongst a large number of values, and if it wasn’t immutable then you could never trust the data you have now is the data you assigned a while ago.
1 Like
Can I ask you to start a new topic for this? It’s going to be hard to find specific bug reports and discussions in this post later.
1 Like
It’s not yet possible to display the user-assigned name of components. I haven’t found a solution yet to this problem I like. I want to avoid vertical text as that’s much harder to read, so the GH1 approach doesn’t work. Whether the icon automatically disappears when you assign a custom name, or whether that remains an option is yet to be seen.
So they’re easier to hit? So many UI decisions have been made in the spur of the moment and are liable to change still. Those pop-up forms were much smaller a few months ago so having huge elements on them wasn’t an issue. Those days are gone now and it’s only going to get worse, so those bug buttons will probably be shrunk sometime soon.
It’s a cat. Cat’s are exceedingly random, which is why I picked that.
12 Likes
I wrote an entire icon display pipeline from scratch because nothing out there did what I really needed. One of the features of this code is that it understands special colours and resolves them only at draw-time. Although you cannot do this yet, it is in principle possible to assign different colours to those special colour codes, so if you don’t like the orange or the blue, that can be changed at runtime without having to reload, let alone redesign the icons themselves.
Replacing the hard-coded colour fallbacks for the Cyan and Yellow to Grape and Lime results in this:
… or just grey:
27 Likes
The cat we had when I was child was very predictable, especially when treats came into play. 
Epic! Love the toned down grey “theme”.
So for meta-data, name:value = key:value = immutable:mutable?
If so, then every new key created would have to be a new type?
Does that mean user-generated keys in Rhino can put used as inputs to GH2, but once inside GH2 the key itself cannot be renamed, but the values can be changed?
Slightly more general question: GH2 is written in C#, an imperative/object-oriented paradigm, but the actual GH2 (and all node-based programming?) scripts are replicating a functional paradigm, so is your approach to make the components act like pure functions as much as possible? (I’m not a programmer, so maybe I’m completely misunderstanding this.)
