I made an add-in to create a pocket for a threaded insert, following the custom pocket example. This turned out to mostly involve changing the code which generates the tool body used to cut the parent body.
What I’d really like to do is to allow this to cut multiple pockets in a manner similar to how the standard hole feature works. If i change the point selection input to allow multiple points to be selected I run into a morass of problems.
i figured that I need to add the dependencies with individual ids, e.g. ‘point0’, ‘point1’ etc. But i find that in some of the handlers the dependencies aren’t set.
The custom pocket example finds the parent body using the selected point, as does my code.
With multiple points each point has it’s own body, although, at least in my use case those should all be the same body. I haven’t found a way to test whether those bodies are identical.
I’m concerned that i might be running into the documented limitation:
This re-compute functionality is currently limited to one specific case. This custom compute functionality should not be used for any other cases and will likely fail. The case where it is supported is where the custom feature consists of only base features, sketches, and combine features. Typically, a custom feature that supports custom compute will have a base feature with one or more B-Rep bodies and a combine feature that uses a Boolean operation to combine the base feature bodies into the parametric model.
is there light at the end of this tunnel?
