Search Issue Tracker
By Design
By Design in 1.8.X
Votes
0
Found in [Package]
1.8.0-pre.2
Issue ID
ISXB-760
Regression
No
The Left Mouse Button is not picked up when listening for an Input while setting the Binding Properties Path in Input System
How to reproduce:
1. Open the attached "ListenLeftMouse.zip" project
2. Open the "Assets/New Controls.inputactions" Asset
3. Create an Action Map by pressing the “+“
4. Add or select any Action of that Action Map
5. Add or select any Binding to that Action
6. Click the “Path” Dropdown menu
7. Click the “Listen” button
8. Click the Left Mouse Button
9. Observe the “Path” box
Expected results: The Left Mouse Button binding comes up when the Left Mouse Button is clicked in Listen
Actual results: Nothing comes up when the Left Mouse Button is clicked while Listening
Reproducible in: 1.6.3, 1.7.0, 1.8.0-pre.1, 1.8.0-pre.2 (2021.3.34f1, 2022.3.18f1, 2023.2.7f1, 2023.3.0b4)
Reproduced on: Windows 11 Pro
Not reproduced on: No other environment tested
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:
We are closing this as By Design. The left mouse button and esc button are special cases that can't really be blocked from their usual function and be caught by the listening UI dialog.
In some far far future we might consider a different solution to this.
Resolution Note (1.8.X):
We are closing this as By Design. The left mouse button and esc button are special cases that can't really be blocked from their usual function and be caught by the listening UI dialog.
In some far far future we might consider a different solution to this.