In addition to Beta1, Beta2 has:
- A fix for MvxLinearLayout refresh issues
- A change of protected API for CreateBindingView in MvxAdapter - it now returns an IMvxListItem instead of an MvxListItem (this method is seldom overridden - but is a breaking change if you did override it)
- A fix for ThreadUtils - Wpf Package
- A fix for ViewModel creation for activities displayed via external Intents - e.g. from Mail or push links
Overall, the features included in 3.0.14 beyond 3.0.13 remain:
- Change to Droid and Touch collections/lists - nullify the datacontexts of individual listview items when removed
- Wpf ThreadUtils assembly has been added
- Improvements in binding parsing of properties beginning with and containing underscores
- Improved error messages when binding fails
- Binding for Android RatingBar control
- ShouldReturn binding for iOS
- Fix to Or logic in ValueCombiner
- Provision for default parameters in ViewModel Init methods
- Inclusion of additional LinkerPleaseInclude entries for Android
- Trace optimisation - no messages shown for null datacontexts
Mind sharing a reason why you decided not to show messages for null datacontexts? I was making an effort of getting ride of those messages when I saw them.
ReplyDeleteThe reason was because the amount of trace was slowing down scrolling after the change that sets list item contexts to null (https://github.com/MvvmCross/MvvmCross/issues/468).
ReplyDeleteAdmittedly this was only for debug builds but the perception was that the scrolling was slow (whereas actually it was just the trace)