RhinoCommon 5 and RhinoCommon 6 have different representations of the objects, although the API is the same

[epignatelli]

Description:

Thanks to @kThorsager, who discovered this issue while dealing with NurbsCurves: #135 and #136.

We found that Rhino.Geometry.ControlPoints, whilst keeping the same API, it asks for a different representation between RhinoCommon v5 and RhinoCommon v6. This is explicit in their documentation as shown below:

Rhino 5

Rhino 6

@kThorsager has gone through the v5 documentation and found the following test script:
https://developer.rhino3d.com/5/api/RhinoCommonWin/html/M_Rhino_Geometry_Collections_NurbsCurvePointList_SetPoint_2.htm#ID0EBBBBA_tab1

If we run this script in the two versions of rhino, we get different behaviours:

Rhino 5

Rhino 6

We need to test all the other Convert methods to understand how spread is the problem.
For the moment, I would advice against using the BHoM with Rhinoceros 6, until we have solved this issue.

The ultimate goal for this issue is to provide full compatibility for Rhinoceros 6.

Test file(s):

You can use the test file in #135

@al-fisher @alelom FYI

[pawelbaran]

Just curious: we've spotted that some curves internalized in GH under Rhino5 were flipped when the same script is opened in Rhino6. Is that something that could relate this issue by any means?

[epignatelli]

It is very probable that the issue is related, in my opinion, but I can't be 100% sure.