Facilitating NAMING things
As much as possible, Blender should ease the work of animators in regards to naming things by defaulting to the name field being active.
This shouldn't affect workflows because unless you start typing immediately, the very next click will pull focus away from the name field.
For instance, when you do a "NEW SCENE" operation, the name field would be active and immediately typing would name the field, while a click anywhere else in the app would pull focus from that field.
tldr: naming should be made as convenient as possible.
9 Comments
Usually, you create a mess before, and then, when it starts to get shape, you will name it properly. Otherwise you will be forced to click after each new datablock. So only optional.
* @ Vyacheslav * All I'm saying is that the name field is active after creation. You can just ignore it and move on if you don't want to use it.
Considering how terrible most people are at naming their stuff, this would help prevent more files from having 120 "cubes".
* @jeric_synergy *
Shift+A will input A in the field instead. So focus should be changed not only with click, but with hovering other areas.
* @ Vyacheslav * , I am not a fan of hovering as a mechanic for changing focus.
* @jeric_synergy * but here it is necessary to disable focus on the text automatically. So we should decide, how it should work without lowering speed.
* @ Vyacheslav * I think you are right, people will be annoyed when they don't want this workflow. But maybe this could be implemented as an optional workflow. So if you want to have it this way, text fields will get focused and if you don't want it (which is the default option) it will continue working as it currently is. This feature itself might not be so commonly used but the implementation if done well could help to decouple the UI components etc.
* @daniel.bisar * the best solution will work as default without lag. So I suggested hover defocus. Blender already have active area detection with hover. Can you suggest anything better for autodefocus? Ideas are welcome.
* @ Vyacheslav * Yea i think autofocus on hover is fine. How exactly would be the workflow for different types of values? For a new scene i guess this is no problem (you click the button, the textbox is near so it can receive the focus without any problems, for new collections this work fine as well, what about objects? - I really like the way jetbrains solves this in rider: you create a new file and get a popup asking for the type (like class, enum, ...) and the name. the field is focused and you give a name and press return. - maybe not the best for blender, but i am just thinking this through a little bit.
If you would add new objects via a context menu in the outliner (which is something that would be cool i think), then this behavior is also no problem. But what about objects you add in the view? Either you would never get the outliner focues (since the mouse is over the 3d view) - so you would not be allowed to move the mouse?
* @daniel.bisar * , the very next click, whereever, will steal the focus from the name field, which you would have to do >anyway<.