generative modeling for Rhino
an incremental update is available. THIS WON'T RUN ON RHINO5 UNTIL THE NEXT R5 WIP GOES OUT!!!!
I'll be travelling for the next week or so, stopping at the Automatic Architecture Event in Delft.
If you need to revert to Grasshopper 0.8.0003, download the installer here.
There is another component in Grasshopper that can do similar things to Orient but with bounding boxes. Box Morph will take your given geometry and morph it to Target Box. Therefore if create twisted boxes based on the normals at the given corner points of your target plane then you can have your geometry follow the surface.
Is anyone else having trouble with this installation? I installed but my grasshopper is still reading 0.8.0001.
I downloaded from the link above, the file is: grasshopper_wip_20101211.exe
Thanks a lot David,
Would it be possible to add an input to the point list component which would change its display colour?
This would help to have several of them displaying simultaneously?
Happy new year!
PS: might be worth being able to control the display colour of each component?
It would involve a per-wire property, instead of a per parameter property. This is something I'll need to do anyway sooner or later, but it does mean I'm not going to do it half-baked before then.
It is possible to write a VB component that does this (see attached).
Hook up the "param" input to any output/floating parameter whose wires you want to change. Then make sure the hidden flag is set correctly and it should either hide or show all the wires going out of it.
Thank a lot David!
Sorry what does per-wire and per-parameter mean ?
When opening the ghx I get an error message saying : "Archive file written with newer version: 0.8.0005" It works very well though !
It would be great if it could also have a "disconnect all" option as well as the hidden one.
I have tried to modify the script to do that but can't find a method related to connection to replace: "recipient.WireDisplay = GH_ParamWireDisplay.hidden".
Ah, currently wire display types are set inside each Parameter. So when a parameter draws its input wires, it knows how to draw them. However, a wire connects twoparameters, so if they both start to specify properties for the wires connecting them, it becomes unclear which parameter has precedence.
The solution is to store there properties on the individual wires instead, something which is completely impossible at the moment and will require a rewrite of large portions of the core program.
The warning is merely there because Grasshopper doesn't know whether a future release has a file format that is compatible with itself. So it just informs you that if there is a problem reading the file, it might be because of this version conflict.
Removing wires is a very different operation from setting wire types. It can be done via a Script component as well, but you could also reconnect all wires using Shift+Control+LMB to a dummy parameter, then delete the dummy.
Here's the answer you're looking for, but maybe not the answer you wanted: http://www.grasshopper3d.com/forum/topics/problem-with-item-index?c...
Yup, not all data is comparable to its own type. Easy enough for numbers and strings and points, but Meshes, Curves and Breps are not trivial. Still, I suppose we would need some sort of equality-comparer in RhinoCommon at some point. I'll see what Steve thinks.