Closed Geokoumpa closed 7 years ago
This is very disappointing because other than this issue,
ya it's a bummer, we will need to fix this. But a good scenario :)
For a tree-view like structure I built a component (in-house), that has no nested list views, but rather just indents items based on their depth in a single list view.
The code slightly more complicated than the straightforward way, but uses much less elements than other approaches and is always fast, no matter how many nodes are open/visible.
Maybe that would work for you as well.
I would gladly try your component as well tp, thanks!
This will probably be fixed on the pack branch.
This will probably be fixed on the pack branch.
maybe, im unsure about this specific use-case though. But i'll be working with @taras this week to fixup @krisselden's code so we can actually merge pack finally. At which point, we should likely add ^^ as a test case.
Hello. Any news on this one? Haivng the same issue and would be glad to have this solved!
I'm sorry we didn't get back to this previously, but at this point this repo is essentially unmaintained. Please use @html-next/vertical-collection or ember-collection for similar functionality.
Closing...
Hello,
I have implemented a multi-level nested tree of collapsible elements, by taking advantage of
and
Everything seemed to work as expected, until some of my data branches had a big number of descendants, such that the total height of the root element was greater than that of the container.
As I start scrolling, at some point, it stops functioning properly, as it shows less items than needed to fill the container area. I have verified that heightForIndex is calculated correctly and accurately. The calculation is done via
where selfAndDescendatsRows is a computed property inside the model that populates the tree / list.
This is very disappointing because other than this issue, the whole system works impressively well, so any help would be much appreciated.
thanks!