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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
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)