Grasshopper 0.7.0049 available for download

Replies to This Discussion

Permalink Reply by David Robles on August 30, 2010 at 4:25pm

awesome! thank you David!

• ▶ Reply

Permalink Reply by Damien Alomar on August 30, 2010 at 9:55pm

Version 0.7.xxx and above break the SDK, as GH was updated to completely use the RhinoCommon. Subsequently, custom components no longer work with newer versions. It is up to developers to update their components so that they can be used with the newer versions.

• ▶ Reply

Permalink Reply by Steve Lewis on August 31, 2010 at 12:51am

Thanks

• ▶ Reply

Permalink Reply by Nathan Howe on August 31, 2010 at 3:31pm

Is it just me or do receivers no longer bake

• ▶ Reply

Permalink Reply by greg bethel on August 31, 2010 at 4:01pm

I know you've described the new Escape abort as rudimentary, but when a Rhino command is exited with the Esc key, Grasshopper thinks the Esc press was applied to it upon the next Grasshopper edit.

Thanks!

• ▶ Reply

Permalink Reply by David Rutten on September 1, 2010 at 7:10am

Thanks, I'll look into it.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

• ▶ Reply

Permalink Reply by David Rutten on September 2, 2010 at 10:11am

Yup, my bad. Instead of watching for Escape key presses I was also watching for Escape key history. This is now fixed.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

• ▶ Reply

Permalink Reply by taz on August 31, 2010 at 4:24pm

My VH didn't update with the new install.

Does it need to update from the internet?

• ▶ Reply

Permalink Reply by Tuan N. Tran on August 31, 2010 at 6:59pm

love the arrows for flatten and graft. many thanks....

• ▶ Reply

Permalink Reply by David Merlin on August 31, 2010 at 8:36pm

I agree with everyone about flatten and graft. It's great! Can the same thing be done for reparameterize?

Thanks David!

• ▶ Reply

Permalink Reply by David Rutten on September 1, 2010 at 7:13am

Hmm, this is getting out of hand. We now have unique symbols for expressions, flattening, grafting and reparameterizing and Lord knows what else in the future. I'm starting to think it might be better to have just a single symbol for anything out of the ordinary and then additional information in the tooltips about what exactly is non-standard about the object.

--
David Rutten
david@mcneel.com
Poprad, Slovakia

• ▶ Reply

Permalink Reply by Evert Amador on September 2, 2010 at 2:48pm

Hi David,

Thanks a lot for the update. I think the point of having a symbol is to make other people aware (and yourself revisiting old definitions) that the parameter has been altered. A simple dot for anything out of the ordinary and the tooltip will do just fine.

Again, Thanks a lot for all this work

Cheers

Evert

• ▶ Reply

• ‹ Previous
• 1
• 2
• 3
• Next ›
• Page