Java member variables which are declared as attributes using declareAttribute() fail to have values set using the @ object instantiation
syntax. In addition, the custom setter() method is not later called.
Together, these create a situation where:
1) Attribute values set using @ syntax that are needed in the constructor do not have those values. Only default values set within the java variable declaration are there.
2) Can't handle it in a custom getter() because custom getters() are not called with @ syntax.
1) After any call to declareAttribute() where there is a @attribute set in the object instantiation in Max, the matching member variable will have the value set with the @ syntax.
2) Immediately after the constructor completes...if there is a custom setter() for an attribute declared with declareAttribute() that has a matching @attribute set in the object instantiation in Max...then the custom setter() will be called.
Personally, I like request #2. That's the intention of a person writing the patch, they are setting that attribute. Therefore, I believe that the custom setter should be called.