Hi Warren, The problem with sticking with an older build is that you're not getting the new enhancements we're doing to fix the issues you found or others that people are working on. For example, the sort bead changed a lot thanks to your report and is not dispatching the same events after my fixes to refresh data on item updates. I even had to change things in other parts.
When I was migrating my apps, and even nowadays, I use to build daily at the start of my day to find possible regression issues and be able to respond as quickly as possible to them. I think after a 1.0 that will be easier to stick in a release version, but we're still doing so much work, so my perception is that it is better to try to keep in the cycle. I'm seeing great improvements these days at all levels (bindings, compiler,...) and all of that will help you find less issues. For example, if you create an example that is not working referring to an older state of the SDK, it can be working in the actual state, so I'll be not able to help you on that. about refreshing in DataGridSort, with my fix, I just need to do " collection.refresh();", but that's because the bead now extends EasyDataProviderChangeNotifier and we're overriding handleDataProviderChanges() to operate for CollectionEvent. COLLECTION_CHANGED events. just my 2... El mié, 30 dic 2020 a las 21:35, wkoch (<[email protected]>) escribió: > I did notice one thing. I can set the columnWidth=0 and then fire a Sort > on > the headerbar. I can set the column back to the original value and sort > again. It all works. > > So I'm wondering if there is something in the Sort bead that we could > hijack > into a forced refresh. > > > > -- > Sent from: http://apache-royale-users.20374.n8.nabble.com/ > -- Carlos Rovira Apache Member & Apache Royale PMC *Apache Software Foundation* http://about.me/carlosrovira
