Yeah… we’re about 500~800 components short of a production ready standard set. Many easy ones are still missing (like Merge or Intersection) but especially many hard ones (like Voronoi and Scripting).
I think we can all agree we just need Voronoi, the rest is distraction !
9 Likes
As a seasoned Grasshopper user, it’s scary how many things in terms of nomenclature have changed.
why the change in names?
this will render basically all tutorials made based on GH1 useless for new users, and experience users will have trouble using it like if they were new users.
its so frustrating trying to use kangaroo, were most of the tutorials are old and names did not carry over to kangaroo2, now that will become a problem with gh2 as well?
1 Like
One of the things that always make me smile is that the export option on rhino has the different file types listed in alphabetical order, please consider doing the same to the named panels, its just so intuitive do look for stuff in alphabetical order.
@DavidRutten looks like components added through double-click search bar are also not pushed to the undo/redo stack
I’d be very surprised if anything except the simplest of possible tutorials would be applicable between versions.
As for the reason why, GH1 was released publicly very early in its life cycle, and I spend years adding and testing new features and approaches. I made a lot of bad decisions and there was very little consistency in the nomenclature. It takes a lot of effort and discipline to keep on top of language consistency.
So far GH2 is basically a 2-person project rather than a 1-person project*, and that second person is in charge of language quality. Both in the UI and the documentation.**
If ever there was a moment in time when a serious jargon overhaul could be justified, it must be now no?
*ignoring all adjacent work done for distribution, UI platforms and the like.
**Proofing is slow and by necessity lags behind development. At the moment a lot of strings in the alpha version haven’t gone through this process yet.
7 Likes
I think a side tab in Grasshopper window like remote control panel (RCP) to add buttons, named views and favorites components will be useful
1 Like
Would be great if I drag a wire from a node and relese the mouse to have a popup (with a search dialog on top) from where to search & choose a desired node.
Wonderful! Thank you david!
Selecting wires is super cool! (but double click to add a relay is no more…)
Anyway, selecting with window is currently a bit problematic because of that, for example when selecting and deleting stuff you also end up deleting unwanted wires:
I think it would be better to remove wire selection in case of windows-selection, and,
as we have SHIFT key to add to a selection and CTRL key to remove from a selection… maybe can we have ALT key as “also select wires” …?
Now a problem from GH1 present also on this GH2 alpha: dragging amount is not equal for every selected component.
I often pack component near each-other with parameters aligned etc etc… after dragging them around a couple of times (even if grouped) everything is dis-aligned again.
(Also, I see some component still have integer coordinates, but some others (like parameters and panel) have decimals coordinates?)
It would be cool that the dragging amount of the mouse cursor is rounded to integer and then applied to the selected components…
I didn’t manage to create groups on GH2, surely still under wip, but i’d like to suggest some control over them via parameters.
Referring to this: How to manage a big definition? Any tips? , for example, I did use a c# to mass-disable every component in a group.
(I would be ok to use again some c# to manually make that by myself, anyway, but the “refreshing waves” are a bit different to manage… )
2 Likes
Took my first steps with Grasshopper 2. A lot of stuff has evidently changed, but there is so many nice things to discover. Amazing work!
First questions/requests:
- Ctrl+Q shortcut for toggling preview ON/OFF is a must-have
- Shortcut G for grafting for example is also mandatory
- I noticed I could reference an edge curve from a Brep, which is nice, but it doesn’t maintain it’s position if the Rhino object changes shape. Is this even possible Rhinocommon-wise to have as a dynamic reference to Rhino “sub-objects” (edges, vertices, faces etc.)?
- Is there an already existing shortcut for creating a panel? I use quotation mark (") all the time in GH1.
You can disable wire window selection in the status bar. I imagine depending on how people work it’s either going to be always on or always off, but still, toggling is not too hard.
This has always been a problem, even in GH1. But yeah, we’ll need proper snapping and possibly some sort of auto-layout. Also possibly just ditching floating point coordinates for objects which don’t support that in their layout, which is making this so much worse.
Good idea. Mass enable/disable and show/hide for all objects in a group would be lovely to have. And yes, there’s no groups yet.
6 Likes
I like the new Tuple container and how it works, but wouldn’t it have been better to call it “map”, “dictionary”, or something similar, since its values get accessed by key, and not integer indices like in many programming languages (to avoid confusion)?
But then it can store various types… maybe your right. 
Well, now that you explained and the existence of proper documentation can eliminate the need for video tutorials, I welcome the change then, sometimes we are too hard on changes and don’t see they exist for a reason. (Guess I am still grumpy with Battlefield Devs lol)
A second feedback/request then… would it be possible to have something similar to the help panel from Rhino in grasshopper? A docked auto-updating help panel that shows the documentation for the last component you placed, I would gladly give up some spance from the canvas in exchange of that, since I am a single monitor/laptop user.
Any chance you can send a link over to what your using as a proxy for the SDK?
Thanks @DavidRutten, I’m gonna just go ahead and ask the BIG question. Any plans on supporting looping natively?
10 Likes
Just do what anemone is doing (similar like Houdini), I’m sure @MateuszZwierzycki wouldn’t mind. It’s the best way to go about it I think.
3 Likes
Yes, loops please!
A “proper documentation” doesn’t eliminate the need for good tutorials.
I believe something like this being worked on. Check this out:
Can we also have “Animate” with Number Slider (I think it’s missing right now)?
3 Likes
I’m sure that’s possible. Good idea.
2 Likes