Wings 3D Development Forum
/
Wings 3D
/
Bug Reports 
/
[ignored] Numeric input fields doesn't consider ","
/
[ignored] Numeric input fields doesn't consider ","
|
[ignored] Numeric input fields doesn't consider ","
|
|
08-20-2015, 11:24 AM
(This post was last modified: 08-26-2015 05:07 PM by dgud.)
Post: #1
|
|||
|
|||
|
[ignored] Numeric input fields doesn't consider ","
As the title says, the numeric input fields (Pressing tab while moving, scaling, etc) doesn't read "," as "." as 1.5.4 did, this means things get moved/scaled/etc. "wrong".
Would it be possible to have Wings3D read it the same way as it did before? Being able to use the numpad greatly increases my speed, but if I can't use the numpad "," key, it's quite disruptive to my workflow. |
|||
|
08-26-2015, 05:17 PM
Post: #2
|
|||
|
|||
|
RE: [ignored] Numeric input fields doesn't consider ","
I agree since I have Swedish computer that uses , as well, but I'm going to ignore this at the moment since it is not easy to do.
I can not convert it since wings allows to write expressions in entry boxes stuff like atan2(34.34, 212.2) where ',' is the delimiter in for arguments. |
|||
|
12-10-2016, 10:45 PM
Post: #3
|
|||
|
|||
|
RE: [ignored] Numeric input fields doesn't consider ","
Does anyone know of a way to chance the input the numeric comma produces? I've tried changing my language and currency settings, but that didn't do the trick.
This thing keeps tripping me up and I'm still have a very hard time getting used to it, despite it having been over a year since it was changed. I understand the reasoning for ignoring it, I suppose, I just wish there was a way I could circumvent it, since I never ever have to use commas in those fields. |
|||
|
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)