TabView from the Windows Community Toolkit is not supported in any platform (except UWP)
The TabView should be working per recent modifications. Could you paste here what's not working ?
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. We don't monitor discussions on closed issues thus please open a new GitHub issue if you need the team to revisit this matter.
I dont know if the correct term is to say that it is not supported but the end result is that if my only page is
<controls:TabView>
<controls:TabViewItem Header="Info">
<TextBlock Text="Test"/>
</controls:TabViewItem>
</controls:TabView>
then for wasm, I get stuck at the launch screen.
I'm on Uno.Microsoft.Toolkit.Uwp.UI.Controls version 5.1.0-build.200.gf9c311b069.
I'd be happy to provide more details and help resolve that issue but I have no clue where to start looking as there is no error whatsoever that I can grab on to start investigating.
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. We don't monitor discussions on closed issues thus please open a new GitHub issue if you need the team to revisit this matter.
I'm trying to fix TabView (from WCT not WinUI) for wasm.
So far here's what I found:
ps: I'll move all this in the Uno.WCT GH once I found all issues.
@FrancoisM
ActualWidth is supported, but it may not be being set with the same timing on Uno as on UWPRepeatButton has been added with @jeromelaban 's PR https://github.com/unoplatform/uno/pull/2290, you might want to retest once the new NuGet package has been created :)ItemContainerGenerator is indeed not supported yetLast issue found:
<VisualStateGroup x:Name="DragStates"> => breaks
I haven't looked into why yet.
Otherwise, I think I've reviewed it all.
From what I remember from the Llama, the ItemsGenerator is not needed per-say for the full behavior of the TabView.
I don't know what ItemsGenerator is to be honest.
But for the usage of items not bounded and directly entered in xaml that line:
ItemContainerGenerator.ItemsChanged += ItemContainerGenerator_ItemsChanged;
can be removed without any impacts.
Also, I didn't figure out why yet but the Back/Forward buttons of the scrollviewer that displays tabs don't work.
This is fixed in the latest dev bits of WCT.