diff options
| author | Joshua Leung <aligorith@gmail.com> | 2018-05-30 17:46:04 +0300 |
|---|---|---|
| committer | Joshua Leung <aligorith@gmail.com> | 2018-05-30 17:46:12 +0300 |
| commit | cdfa5177608d6f78338477b293beb3e92b7335ed (patch) | |
| tree | b5f560b67641ba51a6c826bd0a3c124d83d84852 /release | |
| parent | 23b455a8914aca55732d779ba6f827ddb527a36f (diff) | |
Insert Keyframe: Change default behaviour for how F-Curves get grouped
For many years, animators have been complaining about how keyframing a (transform)
property directly would leave them ungrouped, while keyframing them using a Keying Set
would put them into a group based on the name of the keyingset.
This commit attempts to improve (unify + make consistent) the default behaviour:
* All object transforms now get added to an "Object Transforms" group,
regardless of whether they were added individually via buttons or keyingset
* All bone transforms now get added to a group corresponding to the name of the bone
instead of only the ones added via keyingset
Diffstat (limited to 'release')
| -rw-r--r-- | release/scripts/modules/keyingsets_utils.py | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/release/scripts/modules/keyingsets_utils.py b/release/scripts/modules/keyingsets_utils.py index 7ce5f3e029b..48071117bd4 100644 --- a/release/scripts/modules/keyingsets_utils.py +++ b/release/scripts/modules/keyingsets_utils.py @@ -153,8 +153,10 @@ def get_transform_generators_base_info(data): # no path in this case path = "" - # data on ID-blocks directly should get grouped by the KeyingSet - grouping = None + # transform data on ID-blocks directly should get grouped under a + # hardcoded label ("Object Transforms") so that they get grouped + # consistently when keyframed directly + grouping = "Object Transforms" else: # get the path to the ID-block path = data.path_from_id() |