Announcements
Attention for Customers without Multi-Factor Authentication or Single Sign-On - OTP Verification rolls out April 2025. Read all about it here.

JointOrigin [bug] - python API

pludikar
Collaborator

JointOrigin [bug] - python API

pludikar
Collaborator
Collaborator

Hi,

 

I suspect that a spelling mistake has found its way into the python API.  Browsing a component in VSC I found there are two properties - .jointOrigin and .jointOrgin (missing the "i") - doing a help on both yields exactly the same result.  No sure if that actually causes problems, but it may do.  Certainly doesn't help.

 

Peter

I'm not an expert, but I know enough to be very, very dangerous.

Life long R&D Engineer (retired after 30+ years in Military Communications, Aerospace Robotics and Transport Automation).
0 Likes
Reply
Accepted solutions (1)
383 Views
2 Replies
Replies (2)

BrianEkins
Mentor
Mentor
Accepted solution

You're seeing a bug and the fix for that bug.  The bug was that JointOrigin was misspelled when it was originally released.  We couldn't just change it because if someone had already written some code using it, fixing the spelling would have broken any existing programs.  To get around that limitation we create a new property with the correct spelling.  They both do exactly the same thing.  You notice if you look in the documentation, the misspelled version is not there but for the VS Code Intellisense, there's not a way to have the function available but still "hide" it.

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

pludikar
Collaborator
Collaborator

Ahhh!!  Makes sense now.  Thanks  - I hadn't realised I was digging in an old laundry pile.

 

Peter

I'm not an expert, but I know enough to be very, very dangerous.

Life long R&D Engineer (retired after 30+ years in Military Communications, Aerospace Robotics and Transport Automation).
0 Likes