Grasshopper

algorithmic modeling for Rhino

Minor update with two bug fixes:

  • Expression functions would not load correctly, this is fixed.

  • Surface Normal evaluation would not take orientation into account, this is fixed.

Download from the usual location.

For a more comprehensive list of changes, see the Beta 6 release notes and the Grasshopper Version History available through the GH help menu.

--

David Rutten

david@mcneel.com

Views: 2755

Replies to This Discussion

Great update! I like the new Display Tab. It was always a bit confusing to explain where to find the various display components. 

Just a thought, do you think maybe there needs to be a parameter type for extrusion since rhino 5 added it. I often have say a line that I extrude into a "surface" that rhino 5 classifies as extrusion now. So I try and use the surface param but instead have to use brep or geometry. Not that its a big deal just throwing it out there. 

How do you control the size of the vectors displayed on the new Point Order component? The default seems to be to scale each vector head based on the length of the vector. The result is a bit chaotic and not so helpful compared to the previous Point List component. When this is baked, all the heads are the same size. It would be great if they were the same size in the Gh display component too. 

Hmm, true. The arrowhead is a fixed percentage of the length of the shaft. It was the only way I thought I could make the arrowhead always shorter than the vector.

How about the size of the arrowhead is the lowest of two values, the first being N% of the vector and second being X pixels? That way short vectors still work and the arrows never get too big either.

--

David Rutten

david@mcneel.com

Would it be possible to come up with a solution where all arrowheads have the same size?

--

David Rutten

david@mcneel.com

Whoa! That was quick, but with a few very long lines there still will be large differences in arrow sizes.

What about an algorithm that computes an average between min and max size and uses it as default (per-file solution).

I can make the arrow size depend on the shortest or average line length as well. But in the former case very short segments will ruin the party for everyone.

At the moment no arrow head will be bigger than 20 pixels, no matter how long the line. 

--

David Rutten

david@mcneel.com

True, but this problem exist in a regular technical drawings. What about placing arrows outside short dimensions?

This component is meant mostly for inspecting a collection of points. If you want to actually use these arrows as dimensions, why not create a polyline, explode it and then use the segments for marker dimensions?

That way you can control exactly how large the arrows should be.

--

David Rutten

david@mcneel.com

Attachments:

It looks very elegant and clear now with the same arrow size.

I guess that would work, but what if you made it similar to the plane radius and made the size uniform, but open to the user? So under the Display menu there would be a new setting for Vector Size?

Or, couldn't you just use the same code that you have for the Vector Display component? In that, the size of the vector heads is a fixed pixel size. 

Edit: Ah, I hadn't refreshed in a few minutes and missed all of the previous responses. I think your solution works well. Thanks!

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