Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2019.4.X, 2020.3.X
Votes
1
Found in
2019.4
2019.4.7f1
2020.1
2020.2
2021.1
Issue ID
1299579
Regression
No
[UWP][UI] Cursor is replaced with a black square when Cursor.SetCursor() is called with anything but the Default Cursor
How to reproduce:
1. Open the attached "UWP_Cursor_Repro.zip" project
2. Build and run to UWP (with Executable build type)
3. Click on the "Change Cursor" button and move the mouse
Expected result: The black box is not visible at the cursor position and the SetCursor texture is visible
Actual result: The black box is visible at the cursor position and the SetCursor texture behind it (see UWP Mouse Bug.mp4)
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Notes:
- The issue is not reproducible with XAML or D3D build type
- Could not test on 2018.4, because executable build does not exist in that stream
Comments (1)
-
mrVentures
Apr 10, 2021 19:14
Present in 2019.4.22f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Tile Palette] Sprites not rendering when brush tool "Paint a filled box with active brush" is used for the first time
- Adding available Nodes with longer names in Fragment Context window overflow Fragment Context window in Shader Graph
- "Layer Palette Profile" Asset is automatically applied to the second Terrain but doesn't load any layers
- "Terrain Tools" shortcut conflicts with the Overlays shortcut by default
- Longer Shader Graph Property Reference names breaks VFX Graph Output Particle Node
Resolution Note (fix version 2021.2):
Fixed in: 2021.2.0a19