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 Danny Boyes on November 10, 2010 at 8:06am

A bug in RhinoCommon: http://www.grasshopper3d.com/forum/topics/which-side-to-offset?comm...

Permalink Reply by Peter Mehrtens on November 10, 2010 at 9:02am

one more example of the ListItem component error

Attachments:

ListItem_Component in v0.8.0001.PNG, 64 KB
gh_0_8_0001 ListItem.ghx, 55 KB

Permalink Reply by Danny Boyes on November 10, 2010 at 9:29am

Hi Peter,

Some good news and some bad news for you. This is not the List Item component. It is the Item Index component which will return a -1 if it is unable to identify the point in the list.

In this example it cannot find either the integers 0 or 1 in a list of Referenced Points so therefore a -1 is output.

The good news, in trying to put together an example of the Index component for you I failed to achieve anything other than -1 output. So there is a bug in this component after all.

Permalink Reply by Peter Mehrtens on November 10, 2010 at 10:45am

Thanks Danny.
Ah, of course... I accidentally kept grabbing & dragging the wrong component off the top.
Gosh. I should get some sleep.

Pity - and somewhat a coincidance - that the index item is broken after all.

Permalink Reply by kermin chok on November 15, 2010 at 12:07pm

David,
I seem to be getting a Bake error. Does this version of GH work well

with Rhino 5 64 bit?
Thanks.

kermin

Attachments:

GH Bake Error.jpg, 243 KB

Permalink Reply by David Rutten on November 15, 2010 at 1:29pm

Hi Kermin,

yeah, the bake-via-component-menu is busted in Rhino5. Either use the bake button on the toolbar or switch to Rhino4. This will be fixed once the next Grasshopper goes out.

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

Permalink Reply by kermin chok on November 15, 2010 at 1:38pm

ok.
That's not so bad.

Thanks
Kermin

Permalink Reply by Ali Tabatabai on November 16, 2010 at 8:53am

Hi,

I apologize if this have been discussed before, but I couldn't find any relevant answers to the issue!

or this...

Can any one tel me why this extra step (puting the line/s to a curve component and Re-parametrize it) is necessary to get the parameter function on a curve to work! Did I miss something lately...

Thanks
//A

Permalink Reply by David Rutten on November 16, 2010 at 9:10am

I'll look into this. It's possible this changed in RhinoCommon (not sure yet) so instead of a 0~1 domain for LineCurves it's now always a 0~length domain.

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

Permalink Reply by Ali Tabatabai on November 16, 2010 at 9:17am

OK, thanks.

... another thing though! Why dose it give an error (1st. image) if the value is larger than 0? It should just give a shorter distance.

//A

Permalink Reply by David Rutten on November 16, 2010 at 12:31pm

Well it seems this is actually the standard behaviour. I added some extra code to force the domain of a LineCurve to 0~1 if it's created from a Line, as it does make more sense to me this way, but Curve domains will always be unpredictable. If you want to sample a curve at a parameter you should always make sure the domain has been normalized.

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

Permalink Reply by marcello on November 16, 2010 at 5:06pm

HI,
I noticed this weird thing with the voronoi component. I used same definition as before
Offset now requires a negative number to offset to the inside ( was the other way around ). it will also refuse to offset some of the curves .
Any ideas what may cause this.

Attachments: