Search Issue Tracker
Feature Request
Feature Request in 1.5.X
Votes
1
Found in [Package]
1.0.1
1.5.1
Issue ID
ISXB-456
Regression
No
Just the name of a button is shown in the Event System preview window when pressing on a button if using Input System Package
How to reproduce:
1. Open the user’s attached “MinimalTestCase.zip” project
2. Enter Play Mode
3. Disable “EventSystem (Legacy)” GameObject
4. Enable “EventSystem” GameObject
5. Press on any of the “Button” buttons and observe the information in the Event System preview window
Expected result: A lot of information about the input is logged
Actual result: Just selected button name is logged
Reproducible with: 1.0.1 (2020.3.47f1), 1.5.1 (2020.3.47f1, 2021.3.23f1, 2022.2.16f1, 2023.1.0b12, 2023.2.0a11)
Can’t test with: 1.0.0 (2020.3.47f1) (Errors after project downgrade)
Reproduced on: macOS 13.2.1 (Intel)
Note: Not reproducible with Input Manager (Old)
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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
Resolution Note:
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.
Resolution Note (1.5.X):
Thank you for your bug report.
After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.
The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.