You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure Items exists! I just made it a simple IVector<String>
Expected behavior
Note: this image was taken on Windows 11, where the issue doesn't occur.
I also found that Grids on their own (not inside a ListView) are fine.
Screenshots
It seems like the ColumnDefinition.Width is set to Auto regardless of the value I put in. I was hoping that setting HorizontalAlignment to Right would remedy the issue, but no luck.
I managed to work around this issue by setting the width of the first column to the max width used by my controls/app. Since the second column has to have enough space to be drawn, the first column just gets "clipped" appropriately.
The text was updated successfully, but these errors were encountered:
Describe the bug
On Windows 10, if I have the following setup, the grid's column definitions aren't respected:
Specifically, note the star-sizing on the
ColumnDefinition
s.Steps to reproduce the bug
Items
exists! I just made it a simpleIVector<String>
Expected behavior
Note: this image was taken on Windows 11, where the issue doesn't occur.
I also found that Grids on their own (not inside a ListView) are fine.
Screenshots
It seems like the ColumnDefinition.Width is set to Auto regardless of the value I put in. I was hoping that setting
HorizontalAlignment
toRight
would remedy the issue, but no luck.NuGet package version
WinUI 2 - Microsoft.UI.Xaml 2.8.2Microsoft.UI.Xaml 2.8.7-prerelease.241119001
Windows version
Windows 11 (22H2): Build 22621
Known workaround
I managed to work around this issue by setting the width of the first column to the max width used by my controls/app. Since the second column has to have enough space to be drawn, the first column just gets "clipped" appropriately.
The text was updated successfully, but these errors were encountered: