Porting Triggers

[niels9001]

Current triggers are not fully supported:

FullScreenModeStateTrigger: Uno / WASDK
UserInteractionMode: Uno / WASDK

[michael-hawker]

Fixed XAML Styling, hopefully will see build info now

[michael-hawker]

Seeing issues with DispatcherQueue extension?

"D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj" (default target) (5:58) ->
  D:\a\Windows\Windows\components\Triggers\src\NetworkConnectionStateTrigger.cs(24,28): error CS0176: Member 'DispatcherQueue.GetForCurrentThread()' cannot be accessed with an instance reference; qualify it with a type name instead [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\NetworkConnectionStateTrigger.cs(39,31): error CS1061: 'DispatcherQueue' does not contain a definition for 'EnqueueAsync' and no accessible extension method 'EnqueueAsync' accepting a first argument of type 'DispatcherQueue' could be found (are you missing a using directive or an assembly reference?) [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\NetworkConnectionStateTrigger.cs(42,29): error CS1061: 'DispatcherQueue' does not contain a definition for 'EnqueueAsync' and no accessible extension method 'EnqueueAsync' accepting a first argument of type 'DispatcherQueue' could be found (are you missing a using directive or an assembly reference?) [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]

Does this just depend on #12 now too?

[michael-hawker]

Hopefully the last remaining issues:

"D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj" (default target) (5:63) ->
  D:\a\Windows\Windows\components\Triggers\src\IsEqualStateTrigger.cs(97,22): error CS8509: The switch expression does not handle all possible values of its input type (it is not exhaustive). For example, the pattern '_' is not covered. [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\UserInteractionModeStateTrigger.cs(73,38): error Uno0001: Windows.UI.ViewManagement.UIViewSettings.UserInteractionMode is not implemented in Uno [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\UserInteractionModeStateTrigger.cs(73,38): error Uno0001: Windows.UI.ViewManagement.UIViewSettings.GetForCurrentView() is not implemented in Uno [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\UserHandPreferenceStateTrigger.cs(17,26): error Uno0001: Windows.UI.ViewManagement.UISettings.HandPreference is not implemented in Uno [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\FullScreenModeStateTrigger.cs(43,115): error Uno0001: Windows.UI.ViewManagement.ApplicationView.IsFullScreenMode is not implemented in Uno [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\FullScreenModeStateTrigger.cs(58,40): error Uno0001: Windows.UI.ViewManagement.ApplicationView.IsFullScreenMode is not implemented in Uno [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]

Wonder if we want the ApplicationView based trigger, does that serve a purpose in WinUI 3 world atm? Full screen stuff is handled differently, right?

Leads into the CommunityToolkit/Tooling-Windows-Submodule#33 discussion on what we should do with Uno0001 errors as well and either not raise them as errors (except locally on the WASM head) maybe? Let them flow through so we can identify things folks want to use and point to Uno issues later vs. having to ensure everything works or code it out (as if code it out and Uno releases a build which it works for, then it's still not usable vs. the other way around).

@Arlodotexe I think this just means we need to set Uno0001 as NoWarn (except for the single-component WASM head), right?

[michael-hawker]

Ugh meant to rebase... anyway, @niels9001 the NoWarn was added to main so this should hopefully just build now?

[michael-hawker]

Couple of warnings as errors:

"D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj" (default target) (7:75) ->
  D:\a\Windows\Windows\components\Triggers\src\IsEqualStateTrigger.cs(97,22): error CS8509: The switch expression does not handle all possible values of its input type (it is not exhaustive). For example, the pattern '_' is not covered. [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]
  D:\a\Windows\Windows\components\Triggers\src\UserHandPreferenceStateTrigger.cs(13,35): error CS0649: Field 'UserHandPreferenceStateTrigger.handPreference' is never assigned to, and will always have its default value [D:\a\Windows\Windows\components\Triggers\src\CommunityToolkit.WinUI.Controls.Triggers.csproj]

[michael-hawker]

@niels9001 think we're good, just want to rename the test file?

[michael-hawker]

Sorry for the go around, did a final pass and noticed an extra indentation to a file, and realized we could tidy up another small thing.