I’m really excited about the latest Grasshopper 2 update - great work! I just wanted to point out a few small issues I noticed:
Undo Behavior
Copying a component doesn’t seem to register an undo event.
Scratch Component
The new Scratch component is amazing, but there’s a small issue: when switching between different shapes, the result sometimes changes in an unexpected way.
Path Mapper
I really like the new Path Mapper, especially after reading this issue.
That said, I find the word “map” on the component a bit confusing. Since similar components (like Preset Picker and Constant Picker) don’t have inputs on the left, it took me a while to realize that there is an input there. At first, I even assumed the input itself was named “map,” before realizing it was actually the component name.
I think having the word “map” there might not be necessary and could be misleading. Also, the current placement under Params → Util feels a bit odd to me—I think it would make more sense under Data → Tree.
Grid Components
The Grid components use input names Nx and Ny, which makes sense. However, their metadata uses U and V, which feels inconsistent.
Parameter Editing (wish, not a bug)
At the moment, there’s no way to add new geometry to a parameter once some geometry is already referenced, we have to reselect everything from scratch. I know this mirrors the behavior in GH 1. In GH1, adding geometry to an existing list required using Manage Geometry Collection, and I assume a similar functionality is planned for the Edit Parameter window in GH2.
That said, I have a suggestion: the current “Set one value” and “Set many values” actions in GH2 should not clear the existing values in the parameter. Even the “+” icon on the button suggests additive behavior.
If someone wants to start from scratch, they could simply clear the values manually first. With the new shortcuts, this could work very naturally, for example:
- Right-click + V → add geometry
- Right-click + X + V → clear and then set new geometry
This would make incremental editing much smoother, while still keeping the option to reset values explicit.
Thanks again for the great update, and I’d love to hear your thoughts on this.
@DavidRutten