Well, i am using the +7 and -7 in both versions. It is exactly the same code in the Rhino 6 and 7 versions, but with different results.
I am curious if the Rhino 7 variant is bugged, because it is not offsetting the curve but moving it up and down instead.
the *-1 shouldnt be a problem since this is just a mathematical calculation that will happen. We use a variable offset that we normally offset both directions. For this example is changed our variable name to 7 so it is more readable in the example.
You know, now that I think about it, just the other day I was doing some curve offsets and was frustrated that no matter which viewport I started in it always wanted to offset in the same direction and not the one I wanted. I had to resort to the (relatively) tedious method of clicking the direction option in the command line and providing a “base” vector and a “desired direction” vector. Then it offset along the axis I wanted.
Now that I think about it some more, I may have actually been extruding a solid from a closed curve.
I’m just so accustomed to Rhino commands that don’t work logically that I just find the workaround and don’t give it much more thought.
I don’t know about the changes here, but, as @spb pointed out, new Plane() has no meaning, so I guess the definition is up to the developer. Because it’s a default structure constructor, in .Net, the plane will all be initialized to 0s. You should pick a plane. For example, Plane.WorldXY.
Please post a file as well, if you think there’s more.