Search Issue Tracker
By Design
Votes
0
Found in [Package]
2.0.0-pre.5
Issue ID
1387573
Regression
No
[XR SDK] [XR Interaction Toolkit] UIInputModule.pointerClick event triggered after dragging action is performed
Reproduction steps:
1. Open the user's attached "1387573R.zip" project
2. Open the "UI Interaction" scene
3. Enter the Play mode
4. Click and drag over the UI in the Scene
Expected result: "Pointer Click Event Triggered" message appears in the Console window
Actual result: No message in the Console windows
Reproducible with: 2.0.0-pre.6 (2019.4.35f1, 2020.3.27f1, 2021.2.9f1, 2022.1.0b4, 2022.2.0a2)
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note:
The XRUIInputModule is functioning as expected, and matches the behavior of the other input modules. The pointerClick event should be invoked even if you drag, which is to support pointer down -> drag away -> drag back onto -> release the pointer still being a click, which matches the other input modules.
The dragging property will only be true in the pointerClick event if the target GameObject has a component that implements IDragHandler. If it doesn't have that, such as the Button component, that property will be false even if you begin a drag before releasing to click.
There was a related bug where OnEndDrag was not being called on behaviors that implement IEndDragHandler when the mouse starts a drag, leaves the bounds of the object, and returns to the object to finally release the mouse button, but that was fixed with version 2.0.0-pre.6.