Page MenuHome
Create Task
Maniphest T53154

modal numinput angles units
Closed, ArchivedPublic
Actions

Description

System Information
Debian GNU/Linux 8.8 (jessie)
GeForce GTS 250

Blender Version
2.79 (sub 0), branch: master, commit date: 2017-09-11 10:43, hash: 5bd8ac9abfa

Short description of error
Using modal numinput results in an annoying behavior when scene units are not set to "radians" in case you need to specify a rotation angle as the result of acos/asin/atan functions. The result of these functions is implicitely in radians, and when scene units are set to "degrees", returned values are not transformed to degrees, e.g. acos(0.5) returns 1°. To obtain 60° one as to type acos(0.5)*180/pi.
Setting scene units to radians solves the issue but it's somewhat uncomfortable ;-)

Event Timeline

Vincent Bain (tontonraoul) created this task.Oct 25 2017, 10:06 AM
Bastien Montagne (mont29) changed the task status from Unknown Status to Archived.Oct 25 2017, 8:45 PM
Bastien Montagne (mont29) claimed this task.
Bastien Montagne (mont29) added a subscriber: Bastien Montagne (mont29).

Thanks for the report, but no bug here, if you use trigonometrical functions, then obviously you get radians, up to you to do the conversion. This is essentially a very limited subset of the py interpreter, we can only add a limited level of 'easiness' here, if user want to have full py power then he has to comply to py APIs etc.

Vincent Bain (tontonraoul) added a comment.Oct 25 2017, 9:10 PM

OK Bastien, I agree it's logically inherent to python trigonometric functions -- i.e. results are implicitely in radians. And for whom actually uses these functions it won't be a problem to convert to degrees. But there's still something I call a bug, which is the string returned in the status bar: if I keep on my previous example, typing "r", "x" then "=acos(0.5)" displays: "Rot: [acos(0.5)] = 1° along global X", which is wrong, whatever unit you consider...