--- In flexcoders@yahoogroups.com, "flexrookie" <flexroo...@...> wrote: > > --- In flexcoders@yahoogroups.com, "Amy" <amyblankenship@> wrote: > > > > --- In flexcoders@yahoogroups.com, "flexrookie" <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 in the set data() > > > > override for your renderer. > > > -- > > > can i ask, how would you guarantee that all itemrenderers safely > > > unregister > > > for the UPDATE event? > > > > I'd unregister for the last one (when the renderer is recycled and the > > renderer is now associated with a new object) in the set data() > > override. For completely unregistering it, maybe removedFromStage or > > something like that...? > -- > fair enough, if a bit raw. (i was thinking there might be something > more explicit to kill all the renderers, like a List class dispose() > method.)
That's why I suggested an approach that allows you to use a data only object to handle the data, and not involve the presentation objects.
