Here is a fun interaction thanks to the Mouse Rat plugin. It’s modeled on the dynamic blocks found in autoCAD.
This is for routing circuits. I tried so many methods of getting the routing and order right, including TSP, and it just does not work properly in every instance.
Looks really interesting, especially if it’s supposed to re a replacement for dynamic blocks (I will die on the soap box of this is the single biggest missing feature in Rhino and the only valid reason to use AutoCAD instead). However, I don’t know what you are doing/make/drawing. Can you explain more what you are doing and how you did it?
This is happening in grasshopper, it’s not actually a block. I am developing a plugin for a modular radiant heating and cooling company. These are circuits that enable the user to change the flow direction. Direct interaction is the best way to define those parameters.
How I did it: Other than MouseRat, it’s all vanilla grasshopper nodes. The one special node I used was the data recorder to save the states of the changed direction. The other ways I was thinking of doing this was Kangaroo or GeometryCache but MouseRat seems to be the most computationally efficient method.