Windows
Windows copied to clipboard
FrameworkElementExtensions.Cursor is not available on WASDK target
Describe the bug
As mentioned here:
https://github.com/CommunityToolkit/Windows/blob/321f5ddc8f3bf07865c8f51d992febb25fd7859a/components/Extensions/src/Element/FrameworkElementExtensions.Mouse.cs#L16
the Cursor extension was willingly disabled on WASDK targets during initial porting to v8.
However, I'm fairly sure the extension works on WASDK, as the v7 variant works without any issue.
Steps to reproduce
Try using the sample code for the Cursor extension on a WinUI3 project
<Page
x:Class="Microsoft.Toolkit.Uwp.SampleApp.SamplePages.MouseCursorPage"
xmlns="https://schemas.microsoft.com/winfx/2006/xaml/presentation"
xmlns:x="https://schemas.microsoft.com/winfx/2006/xaml"
xmlns:ui="using:CommunityToolkit.WinUI">
<Grid Background="{ThemeResource ApplicationPageBackgroundThemeBrush}">
<Border
ui:FrameworkElementExtensions.Cursor="Hand"
Width="220" Height="120" Background="DeepSkyBlue"
HorizontalAlignment="Center" VerticalAlignment="Center"/>
</Grid>
</Page>
Expected behavior
I think the #if !WINAPPSDK block for this extension could be removed, making it available on v8.
Screenshots
No response
Code Platform
- [ ] UWP
- [x] 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 10 21H2 (Build 19044)
- [ ] Windows 10 22H2 (Build 19045)
- [x] 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)
- [ ] Windows 10, version 2104 (Build 20348)
- [ ] Windows 11, version 22H2 (Build 22000)
- [ ] 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.