Grasshopper

algorithmic modeling for Rhino

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

Views: 2530

Replies to This Discussion

Still waiting for my lolcat...

--
David Rutten
david@mcneel.com
Seattle, WA
Relative tree item allows you to associate two data items in a tree by specifying an offset.

For example, imagine you have a regular point grid of 10 columns, where each column contains 10 points. So the tree layout would be:

{0;0}(0) (first column, first point)
{0;0}(1) (first column, second point)
{0;0}(2) (first column, third point)
.....
{0;4}(8) (fifth column, ninth point)
.....
{0;9}(9) (last column, last point)

What if you want to connect every point in this grid with a point two levels higher up and one column over?

You can specify an offset like so:

{0;+1}(+2)

If we apply this offset to the list of items above, we'll get:

{0;1}(2) (second column, third point)
{0;1}(3) (second column, fourth point)
{0;1}(4) (second column, fifth point)
.....
{0;5}(0) (sixth column, first point)*
.....
{0;0}(1) (first column, second point)**

* If you overstep the list length and Item Wrap is set to false, you will not get any result. Otherwise you'll get the cycled item.

** If you overstep the number of paths and Path Wrap is set to false, you will not get any result.


At the moment it only supports whole integers, and the items in the offset are simply added to the original path+index. I'm not sure yet if I'll move towards expressions in the offset pattern. There are two components, one allows you to get relative items from the same data tree, the other from two distinct data trees.

--
David Rutten
david@mcneel.com
Seattle, WA
Holy $%$@, this is genius. I gotta try this out.

Thanks again, this looks like a great release.

Marc
Excellent! Thank you for this!
Yeah, Ctrl-Tab switching works perfect now. Thanks!
Thanks for the additions add fixes!!!

could it be that you lost the receivers?

the new abort works very well... do we have to add some code to our components?
in the tests it seams that they are not reacting on the escape hit?
Yep, Receivers gone. No more receivers. You can now set the wire display via parameters directly. A receivers was nothing more than a Generic data parameter with special wire display anyway.

--
David Rutten
david@mcneel.com
Seattle, WA
thanks david
it looks like i read over this addition ;)
btw.... rewiring works like a charm

Hey tomas...

 

What did you mean by "rewiring works like a charm"?  Is there a way to rewire a bunch of output streams at the same time (in order to swap components), or perhaps you meant something else?

Yes hold down Ctrl+Shift then select wire(s) to move. Drag to new component and release

From OP

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

Maybe there is a bug with brepplane intersect function in vb.net script component.I cannot get the intersect curves.The output is just a plane..?
minor bug
pointillist component
if i disable the component the numbers are still visible!

RSS

About

Translate

Search

Photos

  • Add Photos
  • View All

Videos

  • Add Videos
  • View All

© 2024   Created by Scott Davidson.   Powered by

Badges  |  Report an Issue  |  Terms of Service