"A fullscreen mode for the rhino viewport would be really beneficial for interactive stuff or projection mapping in grasshopper.
There is already a rhino command but some viewport naming and also the windows bar are still visible in the actual…"
"Drag and drop is good, but when the nodes are very far apart it's a problem to connect them. I couldn't find how to do it any ather way. I think it's better to use copy/paste connetcion method in advance.
RClick menu over start…"
could you please consider including [DataMatch] (or however you´d like to call it) into Sets-Tree for GH2? Whenever assigning attributes like colours or layer names for baking etc. it is always such a big help.
"Small side note: In order to reduce complexity, maybe you could consider bringing back the old S input at [construct point] and get rid of [point oriented] again.
IMHO S with XY as default would be enough to support its fundamental character,…"
"More than anything I'd like the ability to move input and output locations on a component to the top and bottom edges of components. Actually dragging them along the edges of the component until the right spot is found would be cool. the…"
"The plan is actually to remove both fancy options and display options for GH2. Wires should always be displayed fancily when you might want to see that information. If the end-points of wires are off the screen, then there's little point in…"
"Would be great to be able to change the display mode for wires for all inputs in a multiple selection.
- when doing model clean up and organization, would be great to select a group and then hide all wires in one action
it has been…"
"This also looks like a case where wrapping the data in a dictionary/hashtable would be a good approach. This is fairly straight forward with GHPython and probably C# as well. It'll likely make the component computation substantially faster (as…"
"Today I got a flashback about this topic coding this component...
I know that those outputs could be concentrated in DataTrees and accessed via DataTree operations later (for instance, pExt, pInt, pPed, pPark, etc., could be derived to [0;B;C],…"