On Wednesday 03 Dec 2008, Marco Catunda wrote:
> Yes I could separate IList for each view, but in this approach I don't
> share common data,
> so the memory will increase without needness. I don't know about
> performance...
Have you really got so many items, or users on such constrained hardware,
Hi Jules,
Yes I could separate IList for each view, but in this approach I don't
share common data,
so the memory will increase without needness. I don't know about performance...
I thought ICollectionView (ArrayCollection) for pageaable solution too complex.
All of this complex is for local sort
Hey Marco,
Could you use a separate IList for each view? I don't know how your
implementation works -- but if it's using IViewCursor internally onto
an ArrayCollection or some such, you shouldn't have much performance
hit as they would all be pointing at the same underlying data...
Jules
On Wed,
Hi Jules,
Let me say about my problem. I've developed a class that implements
IList interface for implicit pageable
approach. This class works fine for one data provider of component. If
I use it in two or more components
the list become flicker.
The problem of this flicker is when one component
Hi Marco, first up you have to ask yourself why you want this feature?
There may be another way to solve the problem. However, here's what I
know of your specific question...
Last time I checked (Flex 3 beta 2) there was no *official* way to
inspect the bindings on a component at runtime. However,
Hi,
I have a singleton class with model data provider (like cairngorm model).
Some user interface components binding this model in data provider property.
I didn't find out any way to detect if there is binding in this model
or not, and
how many bindings.
The binding model works with events, so
6 matches
Mail list logo
