Grasshopper 0.8.0002 available for download

Hi All,

Grasshopper 0.8.0002 is available for download. It's been a while since the last release, but I'm working with the core Rhino team for a while so it's hard to focus on continuous development.

Changes since 0.8.0001:

● !! This release is build against .NET 3.5 instead of 2.0 !!

● Added conditional If(condition, A, B) method to the Grasshopper expression language.

● Added Rectangle geometric primitive.

● Added Rectangle3d to the Script type hints.

● Added a FilePath parameter.

● Rectangle and Rectangle 3pt now output Rectangles when appropriate.

● Grid Components now output Rectangles.

● Added a Substrate Component (based on original idea by J. Tarbell).

● Added a FitCrv component.

● Added a Pick'n'Choose component to combine multiple lists into one.

● Added a Collapse Polyline component.

● Added a Planar Surface component.

● Added a Radial Grid component.

● Added zero-length segment removal to the old Polyline component.

● Added two Relative Tree Item components, bit experimental, not sure where to go with this yet.

● Added a Selected-Only filter to the Grasshopper preview.

● Added wire display properties to all floating and input parameters.

● Added Close Document button to the MDI menu.

● Autopanning is now triggered both by Canvas edges and Screen edges.

● Added customized cursors to the Galapagos Genome Linker.

● Rewrote the Timer object. Be on the lookout for breaking behaviour and new bugs.

● Added a new Ctrl+Shift rewiring editing mode for parameter wires.

● Redesigned a bunch of Cursors and removed support for Windows pre-NT cursors.

● Wire Action cursors are now visible before the action begins (i.e. when the mouse hovers over a grip).

● Cursor Resources are now cached instead of loaded from the disk every time.

● Improved Abort icon mouse blocking.

● Rewrote all casting logic to use jump-tables for better performance. Watch out for bugs in data conversion.

● Removed a lot of (over?)cautious validity tests for geometry inputs.

● Twisted Box parameters are now Bake-Aware.

● Updated the QWhale libraries, typing VB and C# code should be somewhat less frustrating.

○ Fixed a bug with multi-line tooltip description layouts.

○ Fixed a bug with surface reparameterization.

○ Fixed the selection rectangle not being visible when no document is loaded.

○ Fixed the Find function short-cut display in the Canvas popup menu.

○ Fixed a bug with AHSL colour components and hue values out of the 0.0~1.0 range.

○ Fixed a bug with Point parameter expression (de)serialization.

○ Fixed a bug with Surface Normal evaluation and flipped surfaces.

○ Fixed a bug with the Bake dialog.

○ Fixed a core SDK problem with the curve offset algorithms.

○ Fixed a bug with number slider menus not working over the rail box.

○ Fixed a potential crash case with the Grasshopper Banner and invalid Library Icons.

○ Fixed a bug with Tiled sampling in the Image Sampler.

○ Fixed excessive undo event recording during Alt+Arrow nudging of Components.

Hope you enjoy these incremental updates. And as always; be sure to back up important work, drive safely, be nice to people you meet and don't pet squirrels, they're flea infested vermin.

David Rutten

david@mcneel.com

Seattle, WA

Replies to This Discussion

Permalink Reply by Claudio on November 22, 2010 at 5:42pm

Added a Planar Surface component

I thought it was there before....no?

Permalink Reply by David Rutten on November 23, 2010 at 1:18am

There was a component for making planar surfaces, but nothing that tests existing surfaces for planarity.

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

Permalink Reply by Sameer Kumar on November 23, 2010 at 3:50pm

Is there any way to also include as output a measure of the non-planarity? For example, the distance between the surface reference plane and the point farthest to it? That would be immensely helpful.

Permalink Reply by David Rutten on November 23, 2010 at 5:21pm

Sorry, I don't have that information and I'm not really sure how to quickly compute that point. It would be fairly easy to do with a mesh though.

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

Permalink Reply by Danny Boyes on November 24, 2010 at 2:19am

Could it be done with a bounding box aligned with the reference plane and then the height would be the distance?

Permalink Reply by greg bethel on November 22, 2010 at 5:57pm

Small bug that's been around for awhile - after 'save as', the new document name updates in the open file listing on the right, but not in the main window title bar (running Win7x64 here).

Love the ctrl+shift multi-wire drag - already used it a few times.

Permalink Reply by Benjamin Golder on November 22, 2010 at 9:53pm

Not sure why, but the Local Code Import component seems to malfunction in this latest version. Specifically, where it once deleted existing geometry and then imported all files, in 0.8.0002 it deletes after importing each file. Attached is the most updated component, along with the VB file. Works normally in 0.7.0057.

Attachments:

LocalCode.gha, 32 KB
LocalCodeImport.vb, 6 KB

Permalink Reply by Vittorio Menna on November 23, 2010 at 8:12am

hi david,
first of all thanx for this new incredible release...
i found a few little bugs which i would like to report:
- as someone else already wrote, the offset component doesn't work sometimes with negative values...
- there's a bug in the data conversion protocol (panel -> expression), see the file attached
best
vittorio

Attachments:

bug.jpg, 39 KB

Permalink Reply by David Rutten on November 23, 2010 at 10:36am

Hi Vittorio,

this is not a bug. The + operator is not defined for number and string. What's 5 + "hello"?
TextPanels output strings and Expressions can operate on strings, so the "500" is not converted to a number.

You can fix this by specifically converting the string yourself, either run the "500" through an integer (or number) parameter, or use a CDbl() or CInt() function inside your expression.

Do you think Expressions should evaluate recursively? I.e. if I run into a String and I cannot handle it, should I try to evaluate that string first?

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

Permalink Reply by Vittorio Menna on November 23, 2010 at 11:28am

hi david,
thanx for your reply,
clear,
by the way, it would be interesting, as u proposed and if i understood correctly, if strings were automatically converted into doubles or int when an expression component cannot handle them... anyway, this is not very important...
best
vittorio

Permalink Reply by Shawn Fernandez on November 23, 2010 at 11:33am

I wouldn't mind seeing the Expression components act more like the other components like accepting post-processed, persistent data, extract parameter etc. Maybe it's too difficult to do this with components that use the Input Manager? Evaluating string input would help it act more like the other components as well.

Permalink Reply by Vittorio Menna on November 23, 2010 at 8:33am

i also found a little bit strange when sometimes, having your cursor on the parameter u want to analyze, the correspondant popup window doesn't show values but data-types information... sometimes, when u want to check the input values, it could be a little bit annoying... see attached image
thanx

Attachments: