I have not found any solution to this so Here my question.
We have large GH project, 2 components are far away each other and to view both
a large zoom scale is needed.
a fast way to connect the wires ?
If I zoom in and start dragging it takes forever and You get lost,
from a large zoom scale You are unable to pick the output of a component due to its small size
I have found no simple way to work out this
any hints or something I am missing ?
Is there a way to hide all the connections and see only those for the selected component ?
this will simplify a lot when it comes to read a GH project made long time ago or by someone else
Use two containers to go between sections of your code. IE do a bunch of manipulations to get a set of points. Put the output into a point object. Then connect it to another point object and bring it to the start of your next operation. It also makes change much easier if you want to change the source of the points.
You can also look at breaking your project up into multiple Grasshopper files or using clusters.
I start dragging a wire while zoomed in, then scroll wheel to zoom out, scroll wheel to zoom on on remote target, finally connect wire and let go of left mouse button.
I’ll admit it’s cumbersome, but then if you have a file so large that you have trouble connecting remote parts of it, I’d say you have deeper problems. On the other hand, GH1 doesn’t provide a huge amount of tools to alleviate these problems, so you’re pretty much stuck between a rock and a hard place.
If you have access to Rhino6, then be sure to check out Wire Relays and Data In/Output components. The former is a useful tool for organising long distance or intersecting/overlapping wires, the latter allow you to split a large file into smaller chunks and pump the data from one chunk into the next.
I would attest to @qythium’s post.
Telepathy can help you organize your canvas in very distinct groups, separated according to functionality.
In an example bellow, there is a small definition where all inputs are on the left, and all outputs on the right:
that way, no matter how many such groups you have on your canvas, there is no spaghetti between them and you can move them (the groups) around as you wish.
In my experience it is best to avoid letting definitions get that big in the first place. Once a gh file gets really large, it’s pretty unlikely it will solve interactively, so there’s not a whole lot of benefit keeping it all together.
I’m a big fan of this approach, Elefront enables you to break projects up into multiple files. For example an architectural project might be structured like this:
where the input for each gh is the previous file. Since Elefront allows you to re-reference your data-structure as it was when it was baked in the previous step, the hassle of re selecting inputs disappears. You can think of each gh file as a node in your project graph as this paper describes.
I find breaking large projects up into multiple files makes maintenance,collaboration and re-use much easier.
Thanks for all the valuable info.
I am aware that big GH definitions should be avoided and clean separation and organization is a must, but when you are searching for a solution the project gets messy, once found the path then you can rebuild and organize it.
For those of us who have to maintain compatibility with Rhino5, is there any way via Python/C# scripting for data trees to be serialized into a file and referenced from another Grasshopper definition?
I’ve been using data = clr.Serialize(param.VolatileData.Value)andparam.SetPersistentData(clr.Deserialize(data)) as an ad-hoc way of saving Grasshopper geometry into JSON files, where param is of type GH_PersistentParam\<T>
But of course this only works when the param tree has a single branch and leaf - when I attempt the above with the entire GH_Structure, it produces a not marked as Serializable error.
wire_selected_a is the selected end of a wire, wire_selected_b is the unselected end of a wire (assuming the other end is selected). If neither end is selected then wire_default is used, unless the wire transports no data, in which case wire_empty is used.
Do note that even if you make wires invisible, they will still ‘be’ there and when you double click a relay may be inserted into seemingly empty space. I predict you will loathe not seeing wires within the hour. You can however make them very transparent.
how can you have multiple wire colours if you just have four xml entries?. How can you override wire appearance. That’s not possible with an unhacked grasshopper. You did not present any possibility to override them traditionally, so I modified it in areas not intended. I’m not sure if this already violates GH License agreements, but as long as I don’t share this, I’m not doing anything illegal
I’m basically just posting that its possible.
So no, I’m not referring to a pirated version of Rhino.
Downloaded Telepathy but it does not show up
I see this message on the Rhino prompt:
Message: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework
I was just joking because cracked copies of Rhino show up as ‘Corporate’. It’s not a real type of license, we only have Commercial, Educational, and Trial (all have the same functionality, it’s only a legal difference).
Since @TomTom (h/cr)acked his Grasshopper I thought it would be more appropriate. To be clear, he’s doing nothing unethical, just unesthetical