A SpeckleKit that supports multiple applications will have multiple toNative() functions for each type of object (one for each application).
The application clients should be able to specify which toNative() method to use.
Actual Behaviour
There does not appear to be any mechanism to select a particular toNative() function. SpeckleCore creates a native object using the first toNative() function that it finds, which might return a native data type for Application A to Application B.
Affected Projects
Clients that use a SpeckleKit that support multiple applications. This is popping up in SpeckleStructuralKit as we add ETABS support.
Reproduction Steps & System Config (win, osx, web, etc.)
Proposed Solution (if any)
Note that this doesn't seem to be a problem with SpeckleCoreGeometry and Revit, Dynamo and Rhino/GH. Is there a simple way to resolve this?
@nic-burgers-arup can provide further colour if required
Step 0:
Expected Behaviour
A SpeckleKit that supports multiple applications will have multiple
toNative()functions for each type of object (one for each application).The application clients should be able to specify which
toNative()method to use.Actual Behaviour
There does not appear to be any mechanism to select a particular
toNative()function. SpeckleCore creates a native object using the firsttoNative()function that it finds, which might return a native data type for Application A to Application B.Affected Projects
Clients that use a SpeckleKit that support multiple applications. This is popping up in SpeckleStructuralKit as we add ETABS support.
Reproduction Steps & System Config (win, osx, web, etc.)
Proposed Solution (if any)
Note that this doesn't seem to be a problem with SpeckleCoreGeometry and Revit, Dynamo and Rhino/GH. Is there a simple way to resolve this?
@nic-burgers-arup can provide further colour if required