Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
0
Found in
2020.3.44f1
2021.3.17f1
2022.2.3f1
2023.1.0a26
Issue ID
UUM-24683
Regression
No
EventType.MouseUp is ignored when used on variable fields
How to reproduce:
1. Open the user-attached “AnimationFPS” project
2. Open the “SampleScene” Scene
3. Select the “Main Camera” GameObject
4. Press on the “Animator” field in the Animation Manager Script Component
5. Open the Console window
6. Notice the printed “dasd” message
7. Press on the numerical value fields e.g: Distance field in Animation Tiers drop-down
Expected result: “dasd” is printed
Actual result: EventType.MouseUp does not work with variable fields
Reproducible with: 2020.3.44f1, 2021.3.17f1, 2022.2.3f1, 2023.1.0a26
Reproduced on: macOS Ventura 13.1 (Intel), Windows 10
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
Hi - Unfortunately we won't be able to support mouse events for OnInspectorGUI due to resource constraints on legacy features. We do encourage users to move on to uitk, which should support the use case described in this ticket:
VisualElement inspectorFoldout = myInspector.Q("Default_Inspector");
RegisterCallback<PointerDown>(() => Do Something)
Resolution Note (2023.1.X):
Hi - Unfortunately we won't be able to support mouse events for OnInspectorGUI due to resource constraints on legacy features. We do encourage users to move on to uitk, which should support the use case described in this ticket:
VisualElement inspectorFoldout = myInspector.Q("Default_Inspector");
RegisterCallback<PointerDown>(() => Do Something)