I found an odd issue with LongListSelector where grouped items would appear in unexpected places at the bottom of the list. I have an app that groups records by name with the first letter of the name in the group header to use as a jumplist. The Aug11 version has a problem when an ObservableCollection is assigned to ItemsSource and the ObservableCollection is populated after assignment, I get unexpected ordering. If I assign an already populated ObservableCollection or a collection from a LINQ query, the ordering is correct. All three cases are properly displayed with the Nov10 toolkit version of the control.
I expect:
a
Alpha
b
Beta
g
Gamma
In the error condition, I get:
a
b
g
Gamma
Beta
Alpha
I'm uploading a small project with a three-pivot app to demonstrate the issue. The first pivot is the error case where the ObservableCollection is populated after assignment, the second is the populated ObservableCollection assigned directly and the third is assignement of the result of the LINQ query.
Comments: Closing fixed issues.
I expect:
a
Alpha
b
Beta
g
Gamma
In the error condition, I get:
a
b
g
Gamma
Beta
Alpha
I'm uploading a small project with a three-pivot app to demonstrate the issue. The first pivot is the error case where the ObservableCollection is populated after assignment, the second is the populated ObservableCollection assigned directly and the third is assignement of the result of the LINQ query.
Comments: Closing fixed issues.