Replies: 1 comment
-
I'd say your second option is the most optimal right now. But it still invalidates the entire struct. We should so something in Slint to support this usecase, for example, we could generating one property per struct fields in the generated code. Right now, if this causes performances problem, you can also try to split the MainListModel struct and use several model: put the "checked" field ouside of the MainListModel, so you have another |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I have model that usually is used in even million of items
which I load into
I tested three possible solutions, but only first not require to copy/clone data, but it not works
Beta Was this translation helpful? Give feedback.
All reactions