Actually it was about eight months ago that I started working with Rhino and all the code in my current company has been developed using Rhino .NET. So I inherited the code. The code is written in C++/CLI.
So I have been thinking would it be better to switch to RhinoCommon with C++/CLI or just move to the Rhino 6 C++ SDK. Personally if I would prefer to rewrite the existing code using Rhino 6 C++ SDK.
It would be great to know your opinion on this.
As far as the offset goes, from your explanation I understood the RhinoOffsetCurveMethod correctly, but still I do not get expected results. I will try to implement it using the RhinoCommon method and get back to you.
If you’re willing to start over, I’d probably steer you more towards using C# instead of C++, unless you have some other reason for using C++. Plug-in written in C# will easily port to Rhino for Mac, and the UI tools are much richer. In fact in V6, we have a cross platform UI toolkit, Eto, included with Rhino.
Thank you very much for your input.
In the mean while I believe that there is a problem with a curve offset method in RhinoCommon as well as Rhino.NET library. I took the following steps:
1.Slice a mesh with planes all of which are parallel to each other
2.The intersection of the planes with the given mesh produces closed planar curves.
3.When trying to offset these curves with an offset distance of 10mm towards outside, the curve offset method does not behave uniformly.
a. In some cases it does not produce any offset
b.In others it produces an open curve
Here is the code using the rhinocommon library. I find with my experiments that offset curves are not always created correctly for any cutting plane given a mesh
The array of contourCurves usually has length 1 and generally the curve is closed. However, the offsetting does not work all the time. It would be great if you could tell me a way to solve this problem.