Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
1.1.0-pre.6
Issue ID
1362056
Regression
No
Simulated Touchscreen does not trigger a button click Events when pressing the same spot consecutively
Reproduction steps:
1. Open the user's attached project
2. Open SampleScene in Assets/Scenes
3. In the Main Menu select Window->Analysis->Input Debugger
4. Disable "Simulate Touch Input from Mouse or Pen" in the Input Debugger window.
5. Enter Play Mode and select Game View
6. Click multiple times on the Button1/Button2 (without moving the cursor)
7. In the Input Debugger window Options enable(select) "Simulate Touch Input from Mouse or Pen"
8. Enter Play Mode and select Game View
9. Click multiple times on the Button1/Button2 (without moving the cursor)
Expected result: Button1 register clicks and changes to Button2 and vice-versa on both input types
Actual result: Buttons do not register clicks on Simulated Touch Input when not moving the cursor
Reproducible with: 1.1.0-preview.3 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1), 1.1.0-pre.6 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1, 2021.2.0b9, 2022.1.0a6)
Couldn't test with: 1.0.2 (2019.4.30f1, 2020.3.17f1, 2021.1.19f1) due to Console error: "Pointer should have exited all objects before being removed"
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
- Prefab override popup is cropped/positioned incorrectly when more than one display is used and a higher display Scale is set
- Opening a dropdown on a small screen results in its instant closing when mouse cursor is pressed where the dropdown is going to be opened
- Only "ArgumentNullException: Value cannot be null" is displayed instead of all the actual errors when opening a project with numerous compilation errors
- MultiColumnListView and MultiColumnTreeView do not change selection on first input when focus is set by code
- SerializedProperty.DataEquals is returning false when SerializedProperty.EqualContents return true
This is a duplicate of issue #1311018