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 David Rutten on November 23, 2010 at 10:44am

Ok, fixed. 0.8.0003 should properly format Script Variants.

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

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

thanx

Permalink Reply by pim marsman on November 23, 2010 at 8:42am

Hi David,

Thanks for the new release.

I have two questions:
- Will the Remote control panel be available again?
- Somehow GH custom preview and colour swatch show x-rayed in rhino viewport, even when it's set to be shaded. See pic attached. I don't know where to start; win 7, DotNet version, rhino 5 WIP, GH 8.002?

Thanks,
Pim.

Permalink Reply by David Rutten on November 24, 2010 at 12:01pm

Hi Pim,

Remote Control Panel is on the list. I'm still waiting for docking dialogs in RhinoCommon.

The x-ray thing, I wonder if it's due to the wire bumping I do in my display. I draw all Grasshopper geometry marginally closer to the camera to avoid it being occluded by Rhino Geometry (if you reference a curve for example, I want to draw my curve on top of the Rhino curve). In extreme cases it will actually draw the wires so far in front that it appears to be x-rayed.

This drawing code could be made smarter.

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

Permalink Reply by Paolo Cappelletto on November 23, 2010 at 9:51am

Can someone explain me the difference between to use the Curve code from the SDK or GH_Curve?
(... and, I guess, this is valid for all the other GH_coding)

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

GH_Curve is how Grasshopper stores curves internally. It most likely doesn't provide useful functionality for scripters. However, creating GH_Curves directly saves a conversion step on my end.

This conversion is very fast, the biggest problem is that the conversion jump tables are not hooked up correctly (like happened now).

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

Permalink Reply by Sameer Kumar on November 23, 2010 at 11:14am

David,

The Sweep2 bug is still unresolved...

It is a major shortcoming for me as the sweep2 component is key to my very large definition originally done in 0.6x version. I just cannot get it to work in either 0.7x or 0.8x versions. I would really appreciate some help.

Permalink Reply by David Rutten on November 24, 2010 at 11:51am

I missed that thread. I found the problem and fixed it. Though Sweep2 still sucks as a general method.

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

Permalink Reply by Sameer Kumar on November 24, 2010 at 12:41pm

Thanks a lot.

I agree with you about Sweep2. I would never use it for serious stuff if I had it my way. Looking forward to the next release!

Permalink Reply by Andrei Raducanu on November 24, 2010 at 6:58am

hi again!

bug alert: the solid union component doesn't work if the B hook has more then 1 values as input.

Permalink Reply by David Rutten on November 24, 2010 at 12:11pm

Hi Andrei,

well that sucks. It's only supposed to work if there's more than one input.

I tested it on some boxed and it seems to union them just fine. Can you post the geometry that fails to union?

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

Permalink Reply by Andrei Raducanu on November 24, 2010 at 4:52pm

I meant intersection, sorry..