On Mar 30, 4:47 pm, "franezi...@gmail.com" <franezi...@gmail.com>
wrote:
> (3) you could have a grid snapping in the node's
> middle point or maybe it would be better to have a toolbar with the
> classic aligning tools
I'll look into this, see if I can come up with some clever alignment
algorithms.
> Point 5 (you can drop a node over a connection to put it in between
> twonodes) can be much more difficult than it is in Fusion but you can
> check for the best match in types of data... I know it's
> complicated...
It's not complicated at all, it's just under-defined. I can quite
easily write some code that inserts a new component into an existing
wire, but since the behaviour is very poorly defined it would be a
confusing tool.
> 11. The other thing that would help legibility is passing the
> connectors of a selected node over the overlapping nodes that are in
> front to see them clearly...
> 12. Pasting should occur in the mouse position and not over the copied
> nodes
hmm, what about Ctrl+Shift+V to paste at mouse location? The mouse may
wonder off the visible Canvas region while you copy something, so I'm
hesitant to make it put the new components somewhere where you might
not see/expect them.
> 13. This one is tough... Grasshopper should be a part of Rhino so that
> every action taken in Rhino had a node representation...
Yeah, I'd love for this to happen, but it would require a rewrite of
all of Rhino. Almost all 20 developers working for 4 years, and that's
not to mention the hundreds of plugins written by other companies... I
think it's safe to say this is not going to happen.
Perhaps the History feature in Rhino itself will become a bit more
flexible and accessible, which will allow me (but only to a degree) to
'read' the history record and convert known History tags into
Grasshopper components.
--
David Rutten
da...@mcneel.com
Robert McNeel & Associates
