mjesteve commented on issue #1263: URL: https://github.com/apache/royale-asjs/issues/1263#issuecomment-3065172206
In my case, I'm using `List`/`VirtualList` components. When pagination is enabled, virtualization becomes less critical, but since the number of records per page is user-configurable, it's generally safer to keep it in place. I was also surprised the first time I noticed this behavior. But if you think about it, when we bind *an object*, what we're actually binding is the reference to that object — not the internal changes to its individual sub-properties or nested elements. I recall reading something on the mailing lists regarding this: to properly track changes in nested elements, we need to manually set up listeners for each item. In my current implementation, I’m using an `ArrayListView` to handle pagination, and when I execute: ```as3 getAsourceAll.list.setItemAt(imodel.selectedItem, nreg); getAsource.setItemAt(imodel.selectedItem, nreginpage); ``` the visual updates on both lists are reflected correctly. You can find examples of this approach in my test project, specifically in the pagination section: [https://github.com/mjesteve/royale-examples-community](https://github.com/mjesteve/royale-examples-community) I'm very interested in your test application. I've been exploring the possibility of combining Jewel and Spectrum components for a while now, and I see you’ve successfully integrated both. Would you be willing to share your test project or provide an example? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@royale.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
