Wholly barbecued barnacles. You have no idea how long I stared at that even after you pointed it out.
Thanks.
As to the second point, is there a way to prevent users from accessing functions we want to keep private?
I have typically structured my addons the way it is recommended, with properties and methods in the main class and all ACES simply calling getters/setters/and functions, but I always had some functions that shouldnʻt be accessed out of order or context and I donʻt really need them exposed to the scripting side in c3 editor.
ex:
//Some complicated task
DoSomething() {
_doPrepThingA();
if(_checkThingB()) {
_doSomething();
_resolveThingA();
}
}
Where DoSomething wraps up all the things that need to happen everytime a user would want to do the thing. But, _doSomething does that thing without the additional checks and is used internally for performance reasons, but shouldnt be available to the user.