koobas.hobune.stream
The question is answered, right answer was accepted
Key "TAB" doesn't select text/value in Inspector
Hi all!
I'm having a little trouble. I'm trying to fast edit text/value in Inspector Window with key "TAB".
1 step. I click in field "Position X". Text in the edit field is fully selected. 
2 step. When i press the "TAB" key, text/value in next field doesn't selected. Just the borders are highlighted. The text is not editable until I click on the field with the mouse.
So, I can't quickly edit multiple fields by keyboard shortcuts TAB - value - TAB - value - TAB - value...
Thanks for the help!
As far as I'm concerned, this question shouldn't be marked as answered and closed. What used to be a single "Tab" key press, has now turned into a "Tab-Enter" combination? Productivity?
This is also happening to me. We used to be able to TAB to the next field to edit without having to press enter. Pretty annoying change.
Definitely shouldn't be marked as closed...though this is likely less of a question to be answered and more of a bug that'll be patched out. I can't imagine they did this on purpose.
Press "Tab", than "Enter" and type what you want.
Hope that helps.
It works. But I remember exactly that in previous versions there was no need to press Enter. Text/value was edited without it.
Unity vervion 2017.2.
Thanks for the help!
Hmm, Well I've never used it myself actually.... Anyway it's a pleasure :p. Good luck with your project
Yep. I just recently updated from 5.6.0f2 to 2017.2 so I clearly remember tabbing between editor values all the time... Now it's different. Weird change to make...
One more "thanks". Not sure what is the logic behind as it breaks the workflow for many of us.
It doesn't work for color editing because "Enter" validate the color.
Hmm, ok try, cntl+j.
So tab to the colour you want, and press cntl+j. That seems to be the alternate option to selecting the value.
Thanks for the replies. I hope there is a way around this. I really dislike how it works right now.
It does not fix the problem, it is merely a workaround.
Please note that this is a bug in Unity and therefore you'll need to wait for it to be fixed.
If you would like to keep track and see when it is fixed, please check out the link here
