blender
/
blender
130
398
Fork 572
Code Issues 6.2k Pull Requests 747 Projects 19 Wiki Activity

Fix T38877: F-Curve modal input is incorrect when set to Imperial units. 

Using length units outside of 3dview does not make sense...
This commit is contained in:
Bastien Montagne 2014-02-28 09:51:05 +01:00
parent e82b5f61fe
commit 96a51e99fb
Notes: blender-bot 2023-02-14 11:06:14 +01:00 
Referenced by issue #38877, F-Curve modal input is incorrect when set to Imperial units.
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
source/blender/editors/transform/transform.c
View File

@ -4075,10 +4075,18 @@ static void initTranslation(TransInfo *t)
copy_v3_fl(t->num.val_inc, t->snap[1]);
t->num.unit_sys = t->scene->unit.system;
t->num.unit_type[0] = B_UNIT_LENGTH;
t->num.unit_type[1] = B_UNIT_LENGTH;
t->num.unit_type[2] = B_UNIT_LENGTH;
if (t->spacetype == SPACE_VIEW3D) {
/* Handling units makes only sense in 3Dview... See T38877. */
t->num.unit_type[0] = B_UNIT_LENGTH;
t->num.unit_type[1] = B_UNIT_LENGTH;
t->num.unit_type[2] = B_UNIT_LENGTH;
}
else {
/* SPACE_IPO, SPACE_ACTION, etc. could use some time units, when we have them... */
t->num.unit_type[0] = B_UNIT_NONE;
t->num.unit_type[1] = B_UNIT_NONE;
t->num.unit_type[2] = B_UNIT_NONE;
}
}
static void headerTranslation(TransInfo *t, float vec[3], char str[MAX_INFO_LEN])