Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

how can I get my "listview" container's items be displayed in a recycleview fashion? #379

Open
K3nn3th2 opened this issue Oct 17, 2019 · 4 comments

Comments

@K3nn3th2
Copy link

As stated, I'm thinking if how to get my listview containers items to be displayed in a recycleview fashion.

My program runs fine when I don't have too many objects in my containers Include.objects list but when it gets crowded the program crashes.

Would I have to use a rawwidget to use a qlistview object? (Which seemingly would support the recycle approach)

@MatthieuDartiailh
Copy link
Member

Could you clarify what you mean by recycle approach ? Also could you post the traceback of the crash and a minimal reproduction example.

@K3nn3th2
Copy link
Author

K3nn3th2 commented Oct 19, 2019

I am thinking of a view like kiwi's Recycleview, which uses a memory efficient approach to display the child widgets.

Or is this already the case in enaml?

When I have a lot of the listitems in the container mentioned here the program runs until I scroll rapidly through the list, then crashes. It only happens when the list is large.

@MatthieuDartiailh
Copy link
Member

No it is not the case in enaml. First, because it does not make sense in an Include that can receive arbitrary widgets. It could be interesting in a Looper but I am not sure how we would do that without tying it to the backend.

@K3nn3th2
Copy link
Author

Thanks for the reply!
Do you suggest wrapping a QListWidget via a RawWidget?
My "ListItems" would have to be QListItems then , am I seeing this correctly?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants