Yes, as allandt suggests, you should provide a default value for
constructor param
Unfortunately, it's not the only problem with components (at least in CS3)
For me, the worst one is about [Inspectable] parameters (and their setters).
As described here
http://www.bit-101.com/blog/?p=1181
setters
could you put your init() method call in a setter?
On Wed, Jan 28, 2009 at 10:27 AM, Gregory N greg.gousa...@gmail.com wrote:
Yes, as allandt suggests, you should provide a default value for
constructor param
Unfortunately, it's not the only problem with components (at least in CS3)
For
could you put your init() method call in a setter?
No :-)
Actually, these [Inspectable] parameters and their setters are not a
*functional* part of component. I mean that, if it's created via code
(using constructor), [Inspectable] parameters are not used.
However, if user has the component in
3 matches
Mail list logo
