Search Issue Tracker
Fixed in 1.0.0-preview.7
Votes
0
Found in [Package]
1.0.0-preview.6
Issue ID
1229146
Regression
Yes
[InputSystem] Reordering of ActionMaps in Input Action window fails and throws "Should have drop target" error
How to reproduce:
1. Open attached project "InputTests.zip" (or create a new project and import Input System package)
2. In Project window, right-click -> Create -> Input Actions
3. Open newly created Input Action
4. In Input Action window, create ~6 "Action Maps"
5. Try to reorder action map 2 with action map 3
Expected result: the action map switch places
Actual result: the action map 2 goes down to the bottom of the list, an error is thrown "Should have drop target"
Reproducible with: 2019.1.14f1 (0.2.6, 0.2.10, 0.9.0), 2019.3.7f1, 2020.1.0b3, 2020.2.0a4 (1.0.0-prev.6)
Not reproducible with: 2018.4.20f1, 2019.1.14f1 (0.2.1)
Could not test with: 2017.4 (New Input System was not yet implemented)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.0.0-preview.7):
Fixed by https://github.com/Unity-Technologies/InputSystem/pull/1107
Verified in: InputSystem (1.0.0-preview.7)