- User Since
- Aug 28 2013, 6:54 AM (280 w, 6 d)
Fri, Jan 11
User error, not a bug.
Thu, Jan 10
Good Lord that's embarrassing, must've been doing stuff too late into the evening.
No, it appears I misread the warnings by thinking they were status messages instead. The properties in question are dynamically created during module registration using setattr, apparently that no longer works? Is there an alternative?
Or am I reading it wrong in that I need to make that property an annotation? If so, this new requirement completely breaks our node creation system, which is based on dynamically creating the node classes based on OSL shader metadata