Since many of the modifiers throw an exception if there isn’t exactly 1 primary axis, is there a built-in controller to maintain that?
I ended up having to put an event on all created axes to check if IsPrimaryAxis changes to True.
If it does, then it goes through all the surfaces other axes and sets the others to False.
Without this, the modifier.XAxis get accessor function throws an exception saying either “too many items found” or “no items found” while looking for the single primary axis.
I have a small sample I can include that demonstrates this, but this seems like I’m just missing something simple…
Ok the answer is:
As a workaround for v3.1 users, we recommend add all your axes then you can set the IsPrimaryAxis flag to whatever you want. The property is only manipulated automatically when axes are added or removed.
However, in v3.2+
So the behaviour in v3.2 is a lot more permissive and perhaps intuitive.
I hope that helps answer your question!
Please login first to submit.