Place " . " After " 0 " Automatically
What?
Idea is simple - for numeric input only blocks automatically place "
.
" character after "
0
" if user continue to typing. For example, instead of giving error message for 01, give 0 and because user press 1 add . after 0 automatically - 01 input gives us 0.1 in Blender.
Why?
Right now as you can see on GIF Blender give error if u try to input some 001 or 01 in to numeric blocks. Blender want to see this "
.
". But why it need to press "
.
" button manually if for this inputs there is no values like 00.01 or 023 - if we place "
0
" as first number and continue to typing we 100% want to place "
.
" next to this "
0
".
From other side in my experience - when I try to type on numpad blindly I often press "
0
" second time instead of "
.
" or "
3
" or even
Enter
. For those who have no numpad it even worse - "
.
" button was far from numbers and if user want to type fast and blindly it still possible to press wrong button.
As always - thanks for reading. Also you can check my other suggestions .
11 Comments
No thank you. I'd prefer, rather than an error, that if I type 023, the result be 23. That's what I typed, that's what should go there.
* @Jason van Gumster * But why? How often you press wrong 0 before 23 when actually you want to get just 23? I can't imagine such cases.
From other side, if you press some 0 and then 23 - in 99 - 100% of cases probably you mean 0.23... Such feature is for saving time to not press 1 additional button each time when it's obviously clear that user mean not 023 but 0.23 and to decrease chance to press wrong button when typing blindly.
0.XXX is very often used value if you modeling something small/middle size in scene with 1 meter unit, verryyyy often ... lots of pressing unnecessary " . "
But of course you can have your own opinion. Try it your self to type 0.XX something with . and without, maybe you find it useful too.
* @IIIFGIII * It happens a lot for me. Since the 0 on the Numpad is large and I'm often hitting it to look at scenes from the Camera view (and then toggle back), I often slip and hit that zero whenever I go to the Numpad to enter a value... and right now, I have to remember to backspace. Other applications, I just type the number I want and the zero gets ignored, like it should.
* @Jason van Gumster * Emmmm ... Ok. Different user experience. I don't use numpad for viewport things at all from very beginning - I remap it all to much comfortable to access combinations of keyboard and mouse wheel/4,5 buttons.
I feel I never pres wrong 0 before numbers - but I absolutely boring of pressing " . " If it need to set values like 0.XX 3 - 4 times at row ... You can be sure somewhere I will press something else but not " . ". Most of all it annoying because I have to slow down work and switch my attention to look at numpad to " see " this dot.
Again - I can be wrong. As we see my UX is not someone else UX. It just something " hey, what you think about this? " .
* @Jason van Gumster * Same when I working with VSE curves - lot of setting values between 0 and 1, lot of unnecessary ". " when it clear that I need 0.XX something. Same for lot of things and workflows.
Anyway - we both understand that this error message is not the best solution. Maybe it need to asking for something switchable for your UX to remove " 0 " and for my UX to place " . " after 0?
* @IIIFGIII * if you want 0.xx just type .xx
* @michael * :) kind of alternative solution. It's first time I hear about this. Thank you.
Accidentally hitting 0 on Numpad is something that i can't consider justified to do more often than any other mistake . In the same time, pressing "." on it, is notably harder than any other number, because for fast writing the hand is directly ["moved to"/"placed in"] the middle of it .
For colors and sometimes in general, you literally need to add "." every single time, so its more than justified to make the adding more convenient than for any other number .
no thanks, when I'm working with CAD data I find myself working with a lot of tabular data and it's faster to mentally process the numbers when they are all the same number of digits. so 100mm, 023mm, 001mm, etc.
Why not? With options to turn this off/on in the user prefs so the everyone can do his own jam, I see no issue.
Absolutely right