Allen Lee

edward
Error handling work is still pending on the TODO list. I'd need to think about how to accommodate something like this in the future because it requires cooking the entire graph to be able to provide them. If don't mind, please log an RFE for this.

Yep,Thx again,waiting for the next version.

edward
Are you referring to string parameters on APEX nodes? Or somewhere else?

I believe so. Many input port require rename, callbacks, TransformObject names, etc. It might not be easy to check these back, and I find it difficult to locate where errors in strings occur. Once I have more links, it will be easier to expose issues. I need to be very cautious and slow.

Or if error messages could indicate a Mismatched string or stream data locations, that would be nice too.

edward
Dropdown menus where and for what purpose? The need for more tutorials is very well understood but we're holding off a little bit as we refine the feature set or else they will quickly go out of date. One thing for sure is adding a lot more auto rigging components so that simplify building common rigs.

Thank you for your response~
I eagerly looking forward to the next version of APEX and the accompanying tutorials.

Given the current stringent process based on strings, I wonder if features like dropdown menus or smart search could be implemented to streamline user input, allowing for quicker experimentation with rig logic.

Any simplification efforts (without compromising flexibility) would be greatly appreciated as optimization.