Hard to use DispatcherQueue/Timer in Labs project #35
Description
Describe the bug
These are in two different namespaces Windows.System for UWP and Microsoft.UI.Dispatching` for WinAppSDK.
We currently don't include these in our global using in https://github.com/CommunityToolkit/Labs-Windows/blob/main/common/GlobalUsings_WinUI.cs
This means it's not easy to just reference DispatcherQueue directly in a Labs experiment, which is probably going to be pretty common.
We should add these namespaces to the global usings and make sure they're easy to use.
I did the same in the Stacked Notifications Behavior here:
Which Rive needed as well.
I'm not as sure why I couldn't just include the root namespace for the DispatcherQueue or if that was just an oversight here when initially diagnosing the issue.
Steps to reproduce
Try and use a DispatcherQueue in an exeperiment
Expected behavior
Shouldn't need to include extra namespaces
Screenshots
No response
Code Platform
- UWP
- WinAppSDK / WinUI 3
- Web Assembly (WASM)
- Android
- iOS
- MacOS
- Linux / GTK
Windows Build Number
- Windows 10 1809 (Build 17763)
- Windows 10 1903 (Build 18362)
- Windows 10 1909 (Build 18363)
- Windows 10 2004 (Build 19041)
- Windows 10 20H2 (Build 19042)
- Windows 10 21H1 (Build 19043)
- Windows 11 21H2 (Build 22000)
- Other (specify)
Other Windows Build number
No response
App minimum and target SDK version
- Windows 10, version 1809 (Build 17763)
- Windows 10, version 1903 (Build 18362)
- Windows 10, version 1909 (Build 18363)
- Windows 10, version 2004 (Build 19041)
- Other (specify)
Other SDK version
No response
Visual Studio Version
No response
Visual Studio Build Number
No response
Device form factor
No response
Additional context
No response
Help us help you
Yes, but only if others can assist.