algorithmic modeling for Rhino
Surfaces have a strictly defined normal vector definition. So if you flip the U direction, the V direction, or if you swap U and V the normal vector will be inverted.
Breps on the other hand have an override for the normal direction. A Brep Face is allowed to invert the normal direction of the underlying surface. This is so we can join surfaces into polysurfaces and have their normals match up without the need to flip directions and trimming curves.
I'm not sure but it could be that the current confusion stems from this brep-face-normal-override flag.
As shown in the screen shot the min curvature 0.04821 is larger than the max curvature 0. If I swap uv in the referenced cylinder the normal vector continues to point outward and the min curvature changes sign. Flipping the normal direction of the referenced surface (the normal flips correctly) has no effect on the sign of the min curvature. The question then is why is flipping the normal direction not changing the sign of the curvature and why is the min curvature shown in the example (0.04281) not being assigned to the max curvature output node when it's numerically greater than 0?
Wish: Ctrl + w = Close document (Like in Photoshop for example)
I don't want to change the existing behaviour, but I added Ctrl+Enter and Shift+Enter overloads. use these combinations to assign the value and close the menu.
Also added Ctrl+W to close.
Is it possible to alter the range of integer sliders? I know the default is set for the length to be at least 10. This is an issue when we have less than 10 items to iterate through, and it makes controlling animation tricky because we get a few duplicates or null frames because the range of the integer slider has to be at least 10 items long.
When I select multiple curves in Rhino and assign them to a GH Curve component (using "Assign Multiple"), the resulting list of Curves is not in the order in which I selected them. (This is also the case with other geometry such as points.) Is this a bug or am I missing something?
the order should be maintained, if not, it's a bug. During point picking the order is displayed by a polyline connecting the points. Are you picking curves one by one or window selecting them?
I was pre-selecting (picking) one-by-one in Rhino and then jumping into grasshopper and choosing "Set Multiple" in the component. But you are right, if I choose "Set Multiple" in the component first and then pick one-by-one in Rhino everything works perfectly fine.