@LeoPedersen wrote:
I rely on labeling the inputs and outputs on all of the components in my definition for clarity. I find this indispensable for fast debugging and adding new functionality to large and complex definitions.
I’m finding that almost all the components I use will accept custom labels but the ones where the number of inputs or outputs is configurable, Addition for example, will not remember their custom labels between sessions and revert to meaningless A, B, C etc.
It seems like the custom label functionality is so close to being complete, I just wish it could be added to these last few components.
I’ve been using the new relays in Grasshopper1 as a clumsy workaround just to label what’s going into these label-less components, but now my definition is crashing Rhino and I have to retreat to Rhino5 where relays are not available in Grasshopper0.9.
Anyhow I’m hoping the custom label functionality will be completed for all Grasshopper components soon. Having custom labels available in most components but not all reduces the usefulness of the custom label practice.
Posts: 4
Participants: 2