diff options
| author | Jeroen Bakker <jeroen@blender.org> | 2019-12-17 14:38:12 +0300 |
|---|---|---|
| committer | Jeroen Bakker <jeroen@blender.org> | 2019-12-18 13:00:50 +0300 |
| commit | 8bab8655393faf51a2a7ee3b267a745b38fc49e5 (patch) | |
| tree | 150776a184502257cb50be1de27cb7b3b97f1c49 /release | |
| parent | 2a35383bb0b49dd7a7ee0c507ec012372587f6e5 (diff) | |
Fix T72289: FreeStyle python error
Introduced by {T67981}. We changed the python API for curve evaluation.
Freestyle still used the old call that failed. This patch updates
FreeStyle to use the new API. I checked other areas in freestyle but it
seemed to be the only `evaluate` for curves that is called directly.
Reviewed By: zeddb
Differential Revision: https://developer.blender.org/D6430
Diffstat (limited to 'release')
| -rw-r--r-- | release/scripts/freestyle/modules/parameter_editor.py | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/release/scripts/freestyle/modules/parameter_editor.py b/release/scripts/freestyle/modules/parameter_editor.py index e74b61ced94..534ee7d65be 100644 --- a/release/scripts/freestyle/modules/parameter_editor.py +++ b/release/scripts/freestyle/modules/parameter_editor.py @@ -188,7 +188,7 @@ class CurveMappingModifier(ScalarBlendModifier): # deprecated: return evaluateCurveMappingF(self.curve, 0, t) curve = self.curve curve.initialize() - result = curve.curves[0].evaluate(t) + result = curve.evaluate(curve=curve.curves[0], position=t) # float precision errors in t can give a very weird result for evaluate. # therefore, bound the result by the curve's min and max values return bound(curve.clip_min_y, result, curve.clip_max_y) |