Hi devs,
in Germany we have this comma button on the numerical keyboard, not a point button.
I have seen lately more and more 3D programs (blender, Godot,…), which accept comma numbers also as point numbers.
This would be very nice, in situations where Rhino is asking for just one value, like in the Gumball:
Thanks
Michael
hi Michael that has been discussed many times many many years back i believe even before the discourse, it unfortunately does not seem to get any much interest by the developers…
Rhino is from all the other apps i know the only one which cripples my fingers. having to jump funny hoops to make a comma gives me a strange feeling in my stomach every time i have to use a point instead…
Hi Michael - got that, thanks.
RH-64708 Numeric entry - accept commas for single numeric entry
-Pascal
Yes, please comma!
Greetings from Germany
Tobi
people should be aware of decimal separator is a dot.
.
I don t want to teach this:
if it is a coordinate you can omit z value
1.23,4.56
instead of
1.23,4.56,0
if you round up this - still a 2d-coordinate:
1,5
and yes … if only there is a numeric input…
1,5 is the same as 1.5
you can also use comma as decimal separator…
and next time, the same students will have problems importing a .csv into excel…
comma separates X,Y,Z
dot separates full numbers and decimals.
an interface will get very un-sharp, if all lazy habits should be integrated.
If you’re angry about your Numpad with German Keyboard layout is sending a “,” (comma) instead of a “.” (point)
do a custom Keyboard layout with Microsoft Keyboard Layout Creator (MSKLC) Version 1.4
and use a per app keyboard layout.
Assign this layout to rhino:
“Start menu” → Settings → Find “Typing settings” → Advanced keyboard settings → check checkbox “Let me use a different input method for each app window”
…
kind regards from a native german speaking person who 's using a completely english set up on the computer. … and some custom solutions for all those nice ö ä ü ß …
i never use these cases you are describing. if i had an option to use , instead of . i would most likely keep it activated.
any other software i know allows for the localized form of separating decimals, Rhino is the only Software to date that i know of that forces me to enter . instead of the usual ,
it is a usability issue of utmost importance, i awkwardly have to knot my fingers because my keyboard is just layouted differently.
Dear @encephalon
I can understand the motivation behind the wish.
But the simple solution is to set up a custom keyboard-layout and assign it to rhino. You can also change Number-Formating (but I believe this is system-wide)
how should a dialog for example for rectangle work ?
_rectangle
→ first point… (click or whatever you like)
→ second point or length ?
should it accept
12,34,56,78 and interpret it as x = 12.34 y = 56.78 ?
will
12,34
(1) x=12, y=34
(2) length = 12.34
the comma will really mess up a lot of stuff and make it more complicated to explain / teach / document.
Do you really want to decide each time, wether a comma is possible or it must be a “.” ?
I think interfaces and inputs should be consistent. Also for muscle memory, ten-finger-keyboard-users, … For me Consistency is more important then allowing as much pseudo-intuitive alternatives…
but as long as it is an option, and is turned off by default…
But i think there is more important stuff, the mcneel team shoul work on.
Dear @Tom_P,
I was neither talking about the comma seperator for X, Y, and Z axes in the command line, nor all other command line inputs.
My wish is for input fields with just one numeric value. This would be a nice speed up, and simplification for most Europeans.
Cheers
Michael
BTW: You don’t have to teach this, this would be just for crazy power users. 
So every time you enter coordinates you still have to use a point.
.
Just for clarification - that is not what RH-64708 is about.
That one is specifically for situations where only a single number is valid input.
-wim
I got that but I think it isn’t very consistent / uniform behaviour if one situation allows entering decimal values after a comma and most other situations still require the point.
The whole decimal separator thing is a can of worms (it’s determined by committees (plural) so what can one expect). The British standard for technical drawing, BS 8888:2020, changes the decimal separator from a point (mandated since 1927) to a comma. This may be an unrecorded sign of the apocalypse. Or it may be widely ignored.
Anyway, please also accommodate the official unicode ⎖ (hex U+2396) decimal marker too (but only on keyboards).
Hey @mikko,
is this something for you? I have seen the Finnish PC keyboard has the same numeric block with a comma, like we have in Germany. I am still annoyed by typing decimal places in e.g. Gumball fields.
Thank you, and greetings to Finnland
Michael
Dear @Michael_Meyer
If you want a more convenient input on your numbpad, you can set a per app keyboard layout / language.
first google hit
No need for McNeel to implement this.
Even if you pop this topic again - it does not mean it represents the majority of german speaking users.
I teach in a lot of universities here in Switzerland, they all use an the english rhino interface.
I have many customers - also in Germany - that use Rhino for production - all cnc machines want a dot as decimal separator.
Excel has a big problem with .csv export / Import if language and number format are not set correct.
The hole decimal separator thing already is a big mess, so please do not make it more complicated.
And
Also Rhino has so many inconsistencies regarding the interface - accepting the comma as decimal separator in single-number - fields will mess it up even more.
And there are commands that ask for “point or number” - and as we are allowed to suppress Z=0.
Will 12,34 be a point x=12, y= 34, z=0 or a Number 12.34 ?
I don t wont to teach all those nasty special cases.
@Wim
If this ever gets implemented:
Do it as an option that is turned off by default
Do it as an option that does not effect language-settings with a dot as separator.
Expect a lot of people contacting support that are angry.
Expect a lot of teachers / coaches that will feedback “it s a mess”.
And maybe focus the developers energy on more important stuff.
thanks.
Tom
I wholeheartedly agree.
This is not rocket science.
It’s easy to create a modified keyboard layout.
And for users of German keyboard layouts an easy enough workaround without any tinkering is simply to use the Liechtenstein layout as it has a different numpad: period instead of a comma!
@Michael_Meyer , it might be. Making the number parser treat comma and point the same when a single number is expected might be the easiest start. Very often in Rhino you can enter either a point or a number though, and those would still work the same.
I personally don’t use the numpad very much, and I have always changed Windows region settings to use point for decimal and comma for list separator, before Rhino even existed, so I’ve never felt the pain associated with the numpad comma.
you have a personal favourite but please dont format all others to represent your own ideas.
nothing you cant set while importing as far as i know.
no it would not, it would be a first step to relieve those using the numpad as intended.
you have that backwards, it is currently more complicated because we can not use the numpad properly.
yes please!
just set up your language settings and/or keyboard layout and you re done.
Hi @mikko,
Making the number parser treat comma and point the same when a single number is expected might be the easiest start
Yes please, a better parser would be nice. I see, and use better parsing in other 3D-apps (blender, Godot,…). Why not improve Rhinos parsing?
Thanks
Michael