Search Issue Tracker
Won't Fix
Won't Fix in 2023.2.X
Votes
1
Found in
2020.3.28f1
2021.2.11f1
2022.1.0b6
2022.2.0a4
2023.1.0a1
2023.2.0a1
Issue ID
UUM-3436
Regression
No
GUIUtility.hotControl changes when drawing a button using GUILayout
Reproduction steps:
1. Open the user's attached "Test.zip" project
2. Open the "SampleScene" Scene
3. Select the "Test" GameObject
4. Move the "Test" GameObject along the X-axis using the Move Tool arrow in the Scene view
5. Move it until the number of the "?" buttons changes
Expected result: GUIUtility.hotControl doesn't change and the focus on the Move Tool arrow isn't lost
Actual result: GUIUtility.hotControl changes and the focus on the Move Tool arrow is lost
Reproducible with: 2020.3.28f1, 2021.2.11f1, 2022.1.0b6, 2022.2.0a4
Couldn't test with: 2019.4.36f1 (Scripting errors, couldn't recreate the issue)
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:
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.
Resolution Note (2023.2.X):
Thank you for bringing this issue to our attention. After careful consideration, we have determined that this issue is not aligned with our current development priorities and focus areas (UI Toolkit). As such, we have decided not to invest time and resources into addressing it. We appreciate your input and understanding, and please let us know if you have any other concerns or issues you would like to report in the future.