To keep my UI's "Delete" command generic, I would like my user interface to support the following behavior relying on ETO reactors instead of custom UI code.
- user command causes a call to deleteddynamicchild to try and delete a user identified (ETO) part.
- for certain parts or certain situations of the same parts, instead of deleting the part, a different action needs to occur, e.g. write a rule on the part.
As I understand it, the way to stop the part deletion is by using the allowdelete? rule.
However, this will stop the predeleteself() method from being fired as well, leaving me with no way to cause my other action to occur.
Anyone have an approach for this?
As we discussed in email, the best way to handle this is on the client side. It is not possible for allowDelete to perform an action, nor is it possible for preDeleteSelf to cancel the deletion.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.
Upgrading to a 2015 product? Make sure to check these out 1st!
Created by the community for the community, Autodesk Exchange Apps for Autodesk Inventor helps you achieve greater speed, accuracy, and automation from concept to manufacturing.