I think the ability to put the metatag at the top of the class is a shortcut for putting it on every public property. In certain cases it can be a huge time saver, but you shouldn't do it "just in case". You should do it because you really want to allow binding to every single property.
Maybe I don't know what you mean by "wrapped in a proxy", but no, nothing like that happens. You still have complete responsibility over what the class does and is. For an overview of what [Bindable(event...)] means, read up on PropertyChangeEvent. I'm not sure what you mean by "sub-property". --- In [email protected], "reflexactions" <[EMAIL PROTECTED]> wrote: > > I've read the docs but they left me wanting to know more! > > According to the docs I can add [Bindable] at the top of a class to > make everything bindable. > Fine but is there a downside to that or do I just blindly make whole > classes bindable "just in case" or do I selectively make bindable only > those properties that I know will need it? > > Does making a class or property bindable result in it being wrapped in > a proxy? > > > If I make a property bindable does it make a difference if I use > [Bindable] or [Bindable(event...)] with respect to sub-properties. > > > tks >
