Grasshopper 0.8.0001 available for download

Dear Everybody,

the first version of the Grasshopper 0.8 series is available for download. The reason we rolled the minor version number is because clusters are available again (yay).

I'm off to work with the core McNeel team in Seattle for about 2 months tomorrow and I wanted to release this before I left. It's a bit rushed, clusters are definitely not as 'finished' as I'd like them to be, but there should be enough there for some good old customer feedback at least.

Just in case I horked something up, you can still download 0.7.0057 here.

Download 0.8.0001 from the usual location.

First a basic new features and bug list, then the warning section. If you don't read the warning section you forfeit any rights to complain about this new release.

● Added a new Cluster Object. This is very young code, expect big (quite possibly breaking) changes in the future.

● Added auto-panning to Drag Object and Draw Wire interactions.

● Added canvas curl UI for drag+drop options.

● Added default values to the Quad-Face and Tri-Face components.

● Added a Tree Split component for separating out branches.

● Drag+Drop with text content now creates a new Panel.

● Curve data can now convert from a Surface/Brep with a single closed edge loop.

● Added runtime message balloon feedback.

● VB and C# script components now update immediately when typehints are changed.

● VB and C# script components now update immediately when input parameter access is changed.

● MoveForward and MoveBackwards arrange options are now available.

● Added a Grasshopper Version field to the status bar.

● GraphMapper can now adjust intervals, points and vectors in addition to just numbers.

● Parameter disconnection menu items now highlight the connection in question on mouse-over.

○ The menu short-cuts for Find and Move Forward were both Ctrl+F. Find is now F3.

○ Any Undo operation would wreck the Redo stack, this no longer happens.

○ Fixed a bug with automatic tooltip resizing.

○ Fixed an erroneous "app" autocomplete member in the C# and VB script members.

○ Fixed a bug in the CurveCurve intersection SDK code that occured with overlaps.

○ Fixed a bug in the PointList display component with stale point data.

○ Fixed a nasty bug with stale document caches and undo/redo.

○ Custom Preview Meshes would always draw wires regardless of the Grasshopper view setting. This is fixed.

The Aforementioned Warning Section

This pertains mostly to clusters. At present there's no way yet to edit the contents of a cluster. You can make clusters from a selection by clicking on the toolbar cluster button (selected objects remain on the canvas, this will change), or by drag+dropping ghx files onto the canvas and selecting the Cluster Insert mode from behind the curl.

Clusters contents can be opened as new documents via the Cluster object menu, but this code is very icky still. You can edit cluster properties by double clicking on one.

It is entirely possible that clusters will change so much in the near future that old clusters might not read correctly from 0.8.0001 files. Do not use them yet on production work and always make backups.

That's it. Enjoy,

David

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by David Rutten on October 26, 2010 at 11:38am

Write something in the Rhino notes panel, select the text and drag+drop it into Grasshopper.

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by Alpha222 on October 27, 2010 at 7:50am

Great！！Thanks for the explaination.

Permalink Reply by Alpha222 on October 26, 2010 at 6:27am

Hi David,

GH 0.8.0001 cant recognize Offset {8e2f63d7-0ec4-43f8-8aac-e105eb92224b} which is of GH v0.6.0012 ??

Permalink Reply by Igo Kommers Wender on October 26, 2010 at 11:47am

Could someone explain what clusters are intended for and how to use it? It is the first time I hear about them and I would like to understand how it works.
Cheers,
Igo

Permalink Reply by Luis Fraguada on October 26, 2010 at 12:03pm

Well, lets say you want to clean up your definition, you could clusterize different sections that perform different functions...like groups, but condensed into a smaller size. Another benefit would be for areas where you are repeating a part of the grasshopper definition, you could condense an area into a cluster and copy paste...It seems there is still work to be done there, but its nice to see them return to GH.

Permalink Reply by Igo Kommers Wender on October 26, 2010 at 12:30pm

Thanks Luis, it sounds great for large definitions. I will try it. One more question: Is it possible transform one cluster in another grasshopper definition (another file) and then to link it to a "main" definition, like an external reference? This would be nice.
Thanks again,
Igo

Permalink Reply by David Rutten on October 27, 2010 at 8:59am

Hi Igo,

this functionality is planned yes.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

Permalink Reply by gt2p on October 27, 2010 at 11:41am

Hi, I'm experiencing some problems with bounding box component in GH. I have a patch geometry modeled in Rhino; when it was created, in patch general options, I checked "automatic trim". So far so good.

In grasshopper 0.8.0001, I set the rhino generated geometry as Brep or Geometry. Then, I try to create a bounding box with the BBox component, and grasshopper does create it but considering the untrimmed patch geometry modeled in rhino, and not the trimmed one, wich is in fact the one that appears in the rhino viewport (of course I want the bounding box to bound the trimmed geometry). In the other hand, the divide surface component works perfectly (that means considering only the trimmed patch geometry), so I don't know why the BBox component doesn't.

The strange thing is that I didn't have this problem in previous versions of GH (0.6.0057 for example)

If anyone could help I'd deeply appreciate it.

Attachments:

bounding-box-problem.jpg, 170 KB

Permalink Reply by David Rutten on October 27, 2010 at 10:01pm

Hi gt2p,

yes, this is a problem with our new SDK. The only solution I have for you is to either Mesh the brep then get the mesh bbox, or write a script for computes boundingboxes. We're looking into this, but it might take a while.

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by David Rutten on October 29, 2010 at 6:38am

I wrote a new SDK algorithm for finding Brep bounding boxes yesterday. It will most likely be available in the next release.

--
David Rutten
david@mcneel.com
Seattle, WA

Permalink Reply by to] on October 29, 2010 at 5:02am