Change in the behavior of BRepBody.deleteMe() method

Change in the behavior of BRepBody.deleteMe() method

nnikbin
Collaborator Collaborator
518 Views
2 Replies
Message 1 of 3

Change in the behavior of BRepBody.deleteMe() method

nnikbin
Collaborator
Collaborator

Hi,

 

Today, after installing February 1, 2017 Update of Fusion 360, I found that one of my add-ins is broken. Debugging the add-in revealed a change in the behavior of deleteMe() method. I do not know whether February 1 update has caused it or some previous updates (perhaps January 26 update).

 

I summarized the old and new behaviors here:

 

Old behavior:

  • Invoking deleteMe() on an occurrence --> deletes the occurrence
  • Invoking deleteMe() on a BRepBody which is the result of a feature (Like SplitBodyFeature or ExtrudeFeature) --> inserts a Remove feature in the timeline

 

New behavior:

  • Invoking deleteMe() on an occurrence --> deletes the occurrence (no change in the behavior)
  • Invoking deleteMe() on a BRepBody which is the result of a feature (Like SplitBodyFeature or ExtrudeFeature) --> deletes the feature (change in the behavior)

 

Suppose you split a sphere from the middle using SplitBodyFeature, then you invoke the deleteMe() on one of the split parts. The new version results a sphere (it deletes the split feature) while the old version results a hemisphere (it removes one split part).

 

I think it may cause some add-ins to function incorrectly, so they will need updates

 

Thanks,

Navid

0 Likes
Accepted solutions (1)
519 Views
2 Replies
Replies (2)
Message 2 of 3

marshaltu
Autodesk
Autodesk
Accepted solution

Hello,

 

The behavior change of the API was intended. We found the old behavior of the API was different from the one in UI and made the correction.

 

Ideally any API behaviors should follow the ones in UI, which can give better expectation to API clients when they use APIs.

 

Unfortunately the addins which depended on the old behavior have to be updated accordingly. Sorry for the confusion. We will try our best to avoid such case in the future.   

 

Thanks,

Marshal



Marshal Tu
Fusion Developer
>
0 Likes
Message 3 of 3

nnikbin
Collaborator
Collaborator

Hello @marshaltu,

 

Thanks for your answer. I totally agree with you that the new behavior is more consistent with UI (and also with the behavior of this method in other parts of the API)

 

Regards,

Navid

0 Likes