Search Issue Tracker
By Design
Votes
0
Found in [Package]
Version 1.0.0
Issue ID
1254136
Regression
No
The context.interaction logs Multitap instead of Tap when clicked once
How to reproduce:
1. Open the attached "Multi-tap and tap input functionality (2019.3.15f1)" project
2. Open the Scenes/SampleScene and enter the Play mode
3. Click in the Game view once
Expected: The context.interaction should be of type Tap
Actual: The context.interaction is of type Multitap
Reproducible with: 2018.4.24f1, 2020.2.0a14
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
- Frame Debugger's Hierarchy is not navigable when connecting it to the project built with the Volumetric Fog
- The number of SetPass Calls is increasing when attaching the Frame Debugger to the Player
- Scrollbar briefly appears in the Package Manager during installation process even when the package list is too short to require scrolling
- Script resets to use the previous Skybox color when saving the Scene changes
- [2D] Sprite Library Editor window throws NullReferenceException error when entering Play Mode with Game View maximised
Resolution Note:
We're chasing a different MultiTap+Tap bug but this particular one behaves as designed. Each interaction goes through a cycle involving a started, a performed, and a canceled phase. When LMB is press, the MultiTap interaction sitting on top of the stack is started and thus a callback on the action is received. When LMB is then released and not pressed again, the MultiTap cancels (without performing) and thus another callback is received.
If the script is modified to read like the following, the MultiTap is never performed except if LMB is in fact double-clicked.
public void Fire(InputAction.CallbackContext context)
{
Debug.Log("Fire!");
if (context.performed && context.interaction is MultiTapInteraction)
Debug.Log( context.interaction );
}