Grasshopper 0.8.0009 available for download

Minor but important update to 0.8.0008. This release fixes three bugs, two of them rather serious:

Curve Offset was completely hosed deep down. Seems to be working a lot better now.
Text Panel text would fade out over time when the zoom dropped below 80%.
One-Over-X component would consistently return the highest possible Integer or Floating point number.

Download the new release from the usual place.

If you didn't see the What's New list for 0.8.0008 you can read it on this post.

David Rutten

david@mcneel.com

Poprad, Slovakia

Replies to This Discussion

Permalink Reply by Dedackelzucht on April 13, 2011 at 4:05am

Thanks a lot! Hope you have got at least some sleep last night :-)

Permalink Reply by David Rutten on April 13, 2011 at 4:08am

I plan to catch up real soon...

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Tudor Cosmatu on April 13, 2011 at 4:19am

thank you david! really fast update! cheers!

Permalink Reply by Mateusz Zwierzycki on April 13, 2011 at 4:57am

Is the polygon center same as centroid ?

Permalink Reply by Danny Boyes on April 13, 2011 at 5:31am

Apart from Centroid converts the closed planar curve into a surface first, which is slower.

And Area won't work on an open Curve where as Polygon Centre will

Permalink Reply by David Rutten on April 13, 2011 at 5:59am

No, polygon centroid is merely the average of all the polygon points (not counting the seam point twice if the polygon is closed). So it's great for finding centroids of clean data such as squares, rectangles, triangles, but it will work really shitty for complicated polylines.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Danny Boyes on April 13, 2011 at 5:33am

Are you saying Offset Curve isn't serious!!! :)

Permalink Reply by Dieter Toews on April 13, 2011 at 11:49am

You are very hard core, amazing work.

Regarding curve offset - Seems a bit picker about its inputs than before. That said I would say that this is low priority given that it is easily worked around (in my case a little bit of polygon reduce was all that was required). I have included a file with the curve that worked before and now doesn't.

Attachments:

1OffendingCurve.3dm, 4 KB

Permalink Reply by Holger on April 13, 2011 at 12:36pm

Thank you David!

I will need considerably more time to understand the new release better...

But there's one thing in it which I don't find elegantly solved: The new ToRadians Component.

As less as a serious Power-User I never even came remotely close to situations where using Radians was useful. I vaguely remember that you once explained why Radians are the superior concept...

Excuse my Ignorance but I've still never use them.

Instead (and I can't count how many times) I took expressions to remap the respective Slots. I found this tedious and wished for long already to at least be able to store the my Degree-Preference as a Preset.

Either globally or inside the Component types.

With the last release Ignorants like me, building Defintions with Degrees can choose between two solutions which both cause work. I the case of the newly added Component however even the file gets bloated.

So while I don't like entering the expression too I will probably go on doing this as I still prefer this over a needlessly large Definiton. I'm sure that has been discussed before but still:

Couldn't the repective Components get toogled to certain Preset-States like Pocket-Calculators?

Or would it be possible to globally invert the User Preference somewhere in Settings?

Both would save me work.

Permalink Reply by David Rutten on April 14, 2011 at 2:15am

Hi Holger,

radians is the de facto standard in mathematics and all programming languages I know. The only exception to this rule is the GDI part of .NET, which insists on using degrees to indicate arc segments, and clockwise degrees at that.

I agree that radians are a lot harder to look at, when I see 1.6345 I have no idea what sort of angle to visualize with that. The problem is that I build Grasshopper on top of existing languages, and going for Radians is the only way to keep the thing uniformly consistent.

I concede that might not be a good enough reason to use this somewhat arcane system. But I don't really know a good alternative either. Switching some parts of Grasshopper to degrees is liable to cause as much confusion as it solves.

David Rutten

david@mcneel.com

Poprad, Slovakia

Permalink Reply by Mateusz Zwierzycki on April 14, 2011 at 2:24am

I can say that radians are really better than degrees, far more elegant.

i.e.:

http://en.wikipedia.org/wiki/Gradian

as you can see gradian is :

pi/200 radian

9/10 degree

Permalink Reply by Holger on April 14, 2011 at 5:32am

Hi Mateusz,