Changed Binding to x:Bind in WrapLayoutSample DataTemplates#820
Conversation
fccb4d0 to
551e4ed
Compare
| </muxc:ItemsRepeater.Layout> | ||
| </muxc:ItemsRepeater> | ||
| </ScrollViewer> | ||
| <muxc:ItemsRepeater x:Name="WrapRepeater" |
There was a problem hiding this comment.
Looks like the ScrollViewer was removed. ItemsRepeater doesn't have a bullt-in ScrollViewer, we should either add it back or use an ItemsView instead, which uses an ItemsRepeater internally but acts more like a ListView than an ItemsControl.
There was a problem hiding this comment.
I did a bit more digging after @Avid29 pointed out that the ScrollViewer was still present over on Discord:
- Bad news is that this PR from 2023 rolled over the "deliberately avoiding the double-nested ScrollViewer problem" source design and didn't change any of the samples that already had a ScrollViewer, so we've uncovered that for follow-up.
- Good news is that the nested ScrollViewer wasn't the source of the performance issue we were seeing with the WrapLayout sample, so reverting that line range back to include it and move us towards the proper gallery-level fix won't cause new issues between now and then.
Let's add the ScrollViewer back and then close this.
|
If we add a scrollviewer, does that create the possibility people will assume it's part of the control..? |
@Jay-o-Way Pretty much no, it's part of the sample and not the components source. The scrollview isn't a part of the control to the same extend that the ItemsRepeater isn't a part of the control. Sample shows off the |
Fixes #515
PR Type
What kind of change does this PR introduce?
Bugfix
What is the current behavior?
WrapLayout appear not to load
What is the new behavior?
WrapLayout items appear properly
PR Checklist
Please check if your PR fulfills the following requirements:
Other information