But then you have to write all the event creation and dispatch, plus
all the getter/setter.
That might be fair enough if you have a handful of props but if this
is a couple of data classes with says 100 props each thats quite a
bit of typing when all you want is a couple of props not to fire
events when they change... unless there is a tool to generate the
code from a list of variables.
Personally in some cases I use custom events and others I am ok with
the default handling, depends on what I am doing as to which is more
suited to the situation.
--- In flexcoders@yahoogroups.com, "Johannes Nel" <[EMAIL PROTECTED]>
wrote:
>
> using custom events with your bindable metadata is not only best
practice
> but allows you to decide which properties you want to refresh.
> [Bindable("myEvent")]
> i would recomend using this at all times.
>
> On Wed, Sep 3, 2008 at 1:04 PM, Josh McDonald <[EMAIL PROTECTED]> wrote:
>
> > What it does is renames your variables, and creates get/set
methods, but
> > it doesn't wrap the whole class.
> >
> > So unfortunately it's either all-or-none with the class-level
[Bindable]
> >
> > -Josh
> >
> > On Wed, Sep 3, 2008 at 9:01 PM, reflexactions
<[EMAIL PROTECTED]>wrote:
> >
> >> 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 flexcoders@yahoogroups.com, "Josh McDonald" <dznuts@>
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
> >> <reflexactions@>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 :: josh@
> >> >
> >>
> >>
> >>
> >> ------------------------------------
> >>
> >> --
> >> 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]
> >
> >
> >
>
>
>
> --
> j:pn
> \\no comment
>
