Ah ok.. I had thought the compiler generated a wrapper or sub class behind the scenes when you used the bindable tag...
Well ok learn something new eahc day... tks --- In [email protected], "Josh McDonald" <[EMAIL PROTECTED]> wrote: > > Nope. [Bindable] on a class doesn't wrap the class, it's just exactly the > same as putting [Bindable] on every public field. > > -Josh > > On Wed, Sep 3, 2008 at 8:45 PM, reflexactions <[EMAIL PROTECTED]>wrote: > > > If I add the Bindable tag at a class level every property is wrapped in > > by a sort of proxy that then raises PropertyChange events as > > appropriate. > > > > This certainly saves a lot of time instead of having to go through a > > class and add Bindable to every single property. > > > > But... > > What if there is one property that I dont want to be Bindable and more > > importantly I dont want it to raise PropertyChange events. > > > > Is there same NonBindable tag to achieve this??? > > > > tks > > > > > > ------------------------------------ > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: > > http://www.mail-archive.com/flexcoders%40yahoogroups.comYahoo! Groups > > Links > > > > > > > > > > > -- > "Therefore, send not to know For whom the bell tolls. It tolls for thee." > > :: Josh 'G-Funk' McDonald > :: 0437 221 380 :: [EMAIL PROTECTED] >
