--- In flexcoders@yahoogroups.com, "flexrookie"
wrote:
>
> --- In flexcoders@yahoogroups.com, "Amy" wrote:
> >
> > --- In flexcoders@yahoogroups.com, "flexrookie"
wrote:
> > >
> > > hi amy,
> > > the manager class approach is interesting, and sounds safe from
a
> > > memory-management perspec
--- In flexcoders@yahoogroups.com, "Amy" wrote:
>
> --- In flexcoders@yahoogroups.com, "flexrookie" wrote:
> >
> > hi amy,
> > the manager class approach is interesting, and sounds safe from a
> > memory-management perspective. thanks!
> >
> > you also wrote:
> >
> > > You could potentially set
--- In flexcoders@yahoogroups.com, "flexrookie" wrote:
>
> hi amy,
> the manager class approach is interesting, and sounds safe from a
> memory-management perspective. thanks!
>
> you also wrote:
>
> > You could potentially set up your itemRenderers to
> > register/unregister for these events i
hi amy,
the manager class approach is interesting, and sounds safe from a
memory-management perspective. thanks!
you also wrote:
> You could potentially set up your itemRenderers to
> register/unregister for these events in the set data()
> override for your renderer.
--
can i ask, how would you
--- In flexcoders@yahoogroups.com, "Tracy Spratt" wrote:
>
> The core concepts are that item renderers need to update their
visual UI
> elements when the associated item changes, and need to update that
item on
> user interaction.
>
>
>
> You assign a dataProvider(StockInfo) to the List, whi
5 matches
Mail list logo