Grasshopper 0.6.0043 available for download

Hi All,

as I'm leaving tomorrow morning for SmartGeometry, this is the last chance for about 2 weeks to upload a new version. I don't think we're quite ready to release a new version, but I don't want to wait even longer.

The usual warnings:

1. DO NOT overwrite old files. Makes copies of old files first. Files written with the new version will not be readable by older versions.

2. DO NOT use this version on critical projects. If something is seriously wrong there won't be time to fix it until mid-december.

Download EXE installer

Download ZIP Installer

A brief overview of changes (not complete):
- Settings are no longer stored in the registry, but instead in xml files in a special folder. This makes it easier to delete them (in case you want to revert to factory defaults), copy them, edit them, share them etc. etc. The folder which contains the settings files can be opened via the [File->Open Settings] menu. Note that many settings files are written when grasshopper closes.

- Toolbar panels have been shrunk. Not all components are now visible on the panels, you have to open up the dropdown to see them all. Not sure yet if this is a good way to go...

- Buttons on toolbar panels are now more logically grouped together.

- New Save on Exit dialog for unsaved files.

- Autosave has been added. By default autosave kicks in just prior to a number of predefined 'risky' operations. You can alter the autosave behaviour via the [File->AutoSave] menu.

- Objects can now be fully disabled. There are new buttons on the Canvas toolbar for this as well as new menu items everywhere. Disabled objects will not collect data and they will not compute solutions. Usually Disabled objects are drawn in dark grey.

- New colour scheme for the GUI. If you're seriously unhappy with the new scheme and you don't mind messing around with xml, feel free to edit the grasshopper_colours.xml file in the Settings folder.

- Gradient object now has custom presets and a custom default. New options available in the Gradient Object Menu.

- Path Mapper object has been replaced. If you're using the old one it will still load correctly, but you'll no longer be able to create a new instance of the old version.

- Remote Control Panel is being reworked. This version contains a semi-functioning one, but I recommend you don't use it at all yet.

- Bunch of new components.

- Bunch of bug-fixes (unfortunately not all reported bugs have been fixed yet)

I probably won't be able to read the forum or my email for a while, so if you're running into serious problems, please revert to the 0.6.0019 build.

--
David Rutten
david@mcneel.com
Robert McNeel & Associates
Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Marc Syp on November 24, 2009 at 2:01pm

Very cool. I was about to take a look at that. Very handy, and a good replacement for the flatten one branch method I was using previously. I still think there could be a Copy Path Structure component and a Shift Branch Paths as well. I will post an example shortly.

Incidentally, a true "flatten one branch level" would use the syntax {0;0;A} for your output paths. Not that it is affecting your data, but you are simplifying your path structure by one level here...

Permalink Reply by Peter Mehrtens on November 24, 2009 at 2:12pm

Oh yes, the path mapper is a good tool in the toolbox along with the other new components.

All of these goodies are making grasshopper probably the best friend of data driven design.

Permalink Reply by Thomas Bildsøe on November 25, 2009 at 7:04am

Hi

Can you see why this does not work?

/Thomas

Permalink Reply by Marc Syp on November 25, 2009 at 9:54am

This fails because you don't have any paths matching your input mask. That is, all of your paths are seven levels deep and you are searching only for 3-level branches in your input mask. Try recreating the entire structure in your input:

{0;A;*;*;*;*;*} -> {0:A}

Don't have any data with that structure but this should theoretically solve your problem.

Marc

Permalink Reply by David Rutten on November 26, 2009 at 1:27pm

Guys, you're not allowed to use wildcards yet in the input mask.

You should always use something like {A, B, C, D, E, ..., X}. Variables and operators are only allowed in the output mask.

--
David Rutten
david@mcneel.com
Leusden, The Netherlands

Permalink Reply by Marc Syp on November 26, 2009 at 2:20pm

Hm. The wildcards in the input mask worked for me... are they not supposed to?

P.S. Happy Thanksgiving!

Permalink Reply by kermin chok on December 4, 2009 at 5:08pm

Hi,
Is there something different with the tree item component?

I start with 100 paths, 11 items each. I want to select every other path and only the first item in each path.

I cull the path list with true false pattern.
I graft the path list so i get a new path for each path item instead of a flat list. (50 paths, one path name each)
I pass that list into a tree item component.
Despite using cross reference, i only get the first item.
I should be getting 50 items in 50 paths.

Does anyone know what could be going on?

Attachments:

Tree Item Issue .jpg, 394 KB

Permalink Reply by Claudio on November 24, 2009 at 9:08pm

Thank you David this will be a happy Xmass

cheers

Permalink Reply by Hyoung-Gul Kook on November 24, 2009 at 10:19pm

Thanks David!
- HG

Permalink Reply by Luis Fraguada on November 25, 2009 at 3:58am

David,

Saving Gradient defaults - Dashed Curves...very nice. Any additions / changes under the hood (SDK) that we should be aware of? You are no longer using the EH_ prefix and have changed to GH_ on the SDK functions?

Best,
Luis

Permalink Reply by Benjamin Golder on November 25, 2009 at 12:02pm

Thank you David!!

Excellent changes and additions. I love it. Beautiful work.
And I just spent 5 minutes undoing and redoing over and over with a huge smile on my face.

Permalink Reply by Tore Banke on November 25, 2009 at 1:38pm

Wery nice...

It would be nice to have the possibility to make all the toolbars visable and not have to use the drop down menu.

Looking forward to see some people messing with the xml color file......... - great idea´;)

/// Tore