Search Issue Tracker
By Design
By Design in 6000.0.X
Votes
0
Found in
2021.3.37f1
2022.3.24f1
2023.2.18f1
6000.0.0b14
Issue ID
UUM-68720
Regression
No
PointerEventData.clickCount value is always 1 less than it should be in IPointerDownHandler.OnPointerDown()
Reproduction steps:
1. Open the attached “repro_IN-72839“ project
2. Open the “/Assets/Scenes/SampleScene.unity“
3. Enter the Play Mode
4. Double-click on the white square
5. Observe the Console
Expected result: The “clickCount” value is 2
Actual result: The “clickCount” value is 1
Reproducible with: 2021.3.37f1, 2022.3.24f1, 2023.2.18f1, 6000.0.0b14
Reproducible on: macOS 14.0 Sonoma (user’s), Windows 10 (22H2)
Not reproducible on: No other environments tested
Notes:
- Reproducible in Player
- “PointerEventData.clickCount” indicates the number of successive clicks correctly (1 for a single-click and 2 for a double-click) in “IPointerUpHandler.OnPointerUp()”, but not in “IPointerDownHandler.OnPointerDown()”
- Reproduced on both “StandaloneInputModule“ and “InputSystemUIInputModule“
- On 2021.3.37f1, the count starts with the number that indicates the last amount of successive clicks
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
The processing of the click count may happen on pointer up or down, depending on the event system implementation. This is not a bug, it's behaving as designed, as in this case the count increments on pointer release, not on being pressed.
Resolution Note (6000.0.X):
The processing of the click count may happen on pointer up or down, depending on the event system implementation. This is not a bug, it's behaving as designed, as in this case the count increments on pointer release, not on being pressed.