API inconsistencies

API inconsistencies

MortenGuldager
Participant Participant
497 Views
2 Replies
Message 1 of 3

API inconsistencies

MortenGuldager
Participant
Participant

There appears to be some inconsistencies in the API implementation regarding export option creations:

  • createFusionArchiveExportOptions(filename, geometry)
  • createSTLExportOptions(geometry, filename)
  • createSTEPExportOptions(filename, geometry)
  • createC3MFExportOptions(geometry, filename)
  • createIGESExportOptions(filename, geometry)

Notice how filename and geometry switches order.

 

If this is intentional I would like to hear the rationale behind. For now I'm just confused.

Accepted solutions (1)
498 Views
2 Replies
Replies (2)
Message 2 of 3

BrianEkins
Mentor
Mentor
Accepted solution

There's nothing intentional and I would consider it a mistake.  Unfortunately, once mistakes like this go out there's no changing them because it would break any existing programs that use it.

---------------------------------------------------------------
Brian Ekins
Inventor and Fusion 360 API Expert
Website/Blog: https://EkinsSolutions.com
0 Likes
Message 3 of 3

MortenGuldager
Participant
Participant

Ok, got it. Thanks for clarifying. For now I have generalized their calls in a small wrapper and I am rolling again 😀 

0 Likes