Search Issue Tracker
Fixed
Votes
0
Found in
3.0.0a2
Issue ID
344107
Regression
No
Inspector takes focus unnecessarily when editing parameters
Inspector takes focus unnecessarily when editing parameters
I often need to change parameters on a number of objects in the hierarchy view. To do this, my current workflow is:
1. Click an object in the hierarchy view
2. Change the parameter in the inspector
3. Click the next object
4. repeat
For parameters that do not require a change of focus, such as sliders, drop-down menus, checkboxes, and references, it would be really nice to be able to do the following:
1. Click an object in the hierarchy view
2. Click the checkbox, or whatever
3. Push the down arrow on the keyboard
4. repeat
Unfortunately, the inspector takes focus whenever you click anything in it. I find this frustrating behaviour, because (unless I'm missing it) there is no purpose to inspector focus other than being able to move through inspector variables with the arrow keys. However, editing the above types of variables does not require or benefit from focus. Checking/unchecking checkboxes doesn't even highlight the variable in question, even though it brings focus to the inspector.
Keyboard controls in the inspector seem to be dodgy at best. While it is possible to highlight booleans and references in the inspector, I am not aware of any way to edit them from the keyboard. The user must instead click them with the mouse.
If the inspector is going to take focus with every click that falls into it, that focus should be useful for more than just editing number and string fields. Otherwise, it should not grab focus.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
shubhamswaraj2021
Aug 22, 2020 11:51
good one <a href="https://www.lyricsauto.com">lyricsauto</a>