diff options
author | Joshua Leung <aligorith@gmail.com> | 2013-11-04 08:18:28 +0400 |
---|---|---|
committer | Joshua Leung <aligorith@gmail.com> | 2013-11-04 08:18:28 +0400 |
commit | a1d553a8f388f1e4064b5c80dd9a9621d8172eb3 (patch) | |
tree | bcfc8c7338e69599a610bf7a6614ef5e1ed1f0a7 /source/blender/blenkernel/BKE_mask.h | |
parent | 0b2d9ffaebc04214a65977b2c6f189aae262439b (diff) |
Bugfix [#36950] Restrict Frame Range not being obeyed on Driver F-Curves
By default, drivers (used to) automatically map the driver result (i.e.
"evaltime" or the x-coordinates in the driver graphs) to results. This evaltime
=> cvalue mapping is necessary when there are absolutely no keyframes or
modifiers on a driver F-Curve, or else nothing would happen.
However, when there are modifiers on these driver F-Curves, and these modifiers
only work within certain ranges, there would be confusing and unwanted
situations where even if you clamped the modifiers to only generating a curve
within certain frame ranges, the final driver output would still ignore the
results of the curve due to the underlying 1-1 mapping.
This commit introduces a check to ensure that this automatic mapping won't
happen during such invalid ranges.
Diffstat (limited to 'source/blender/blenkernel/BKE_mask.h')
0 files changed, 0 insertions, 0 deletions