topic Re: SplitFaceFeature in direct edit mode returns None in Fusion API and Scripts Forum

SplitFaceFeature in direct edit mode returns None

mcd8604 — Tue, 21 Dec 2021 05:03:11 GMT

I was really hoping that I would be able to grab the collection of faces from the SplitFaceFeature, but it always returns None/null in direct edit mode (a requirement of my current use case). The component.features.splitFaceFeatures remains empty as well. Is there any simple way to get the modified faces or the newly created edges resulting from a SplitFaceFeature?

Thanks,

Mike

Re: SplitFaceFeature in direct edit mode returns None

mcd8604 — Tue, 21 Dec 2021 05:22:09 GMT

Actually, it wasn't as difficult as I thought it would be. I just create a list prior to the split and compare the entities from the body after the split:

edgesPrior = [edge for edge in body.edges] .. split face code .. edgesNew = [edge for edge in body.edges if edge not in edgesPrior]

I won't mark this as a solution for now in case someone has a better solution.

Re: SplitFaceFeature in direct edit mode returns None

j.han97 — Thu, 23 Dec 2021 02:54:53 GMT

Hi @mcd8604 ,

The fact that all (or most) features called in direct edit mode do not return the respective Feature object is weird to me. Reading the documentation, it feels like they are actually supposed to return something instead of None.

Nonetheless, it is the state of the API now and we can only develop some workarounds (like what you have done here).

Re: SplitFaceFeature in direct edit mode returns None

mcd8604 — Thu, 23 Dec 2021 07:16:20 GMT

Yea, it's unfortunate. My guess is that some or most of the features get disposed of at some point. Then, if a handle was returned through the API then it would become invalid at the time of disposal. That or it was already disposed and there is no handle to return, hence the None. I have no idea though, this is pure speculation.

Re: SplitFaceFeature in direct edit mode returns None

kandennti — Thu, 23 Dec 2021 08:05:41 GMT

Hi.

Running SplitFace in the GUI does not add the feature to the browser tree.

I assume the same is true for the API.