Search Issue Tracker
Fixed in 1.0.0-preview.15
Votes
2
Found in [Package]
1.0.0-preview.9
Issue ID
1287927
Regression
No
[UI Toolkit] Pointer events are triggered multiple times when simulating touch input from mouse or pen with Input System package
How to reproduce:
1. Open the attached "1287927 repro" project
2. Open the Input Debug window from Window > Analysis > Input Debugger
3. Click on the Options dropdown menu in the Input Debug window
4. Enable Simulate Touch Input From Mouse or Pen
5. Open the "SampleScene" Scene from the Assets > Scenes folder
6. Enter Play Mode
7. Click on the red rectangle in the Game window
8. Open the Console windows from Window > General > Console
Expected results: 1 message "t" is logged
Actual results: 2 or 3 messages "t" are logged depending if the mouse was moved while clicking or not
Reprocudible with: 1.0.0-preview.7 (2020.2.0b2), 1.0.0-preview.9 (2020.1.11f1, 2020.2.0b2)
Could not test with: 2018.4.28f1, 2019.4.14f1 (UI Toolkit not available), 2020.2.0b3, and newer (UI Toolkit doesn't compile)
Notes:
-This seems to be happening because the "Click" Action of the "UIToolkitInputActions" Asset (included with the UI Toolkit package) is triggering the PointerDownEvent from the Mouse Binding as well as from the Touchscreen Binding
-Moving the mouse while the left mouse button is still pressed will print one additional message
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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
Resolution Note (fix version 1.0.0-preview.15):
Fixed in 1.0.0-preview.15