blender/source
Joshua Leung fdfcbfd040 Fix T52009: F-Curve "Stepped interpolation" modifier "restrict frame-range" IN and OUT parameters cannot be edited
The problem here was that the "frame_start" and "frame_end" RNA properties of
the Stepped FModifier were shadowing/overriding "frame_start" and "frame_end"
properties of the base FModifier. As a result, when the range() callback
for the In/Out parameters (defined as part of the base FModifier) checked
it's start/end properties, they were always still zero, meaning that the
acceptable range for the In/Out parameters was 0 -> 0 = 0.

Note:
If you've got old files with this problem, you'll need to manually click on
the frame_start/end properties to flush out the old values. It's probably
not worth the effort of applying a version patch for this (given that this
modifier is not one of the most often used ones AFAIK).
2017-07-11 23:33:24 +12:00
..
blender Fix T52009: F-Curve "Stepped interpolation" modifier "restrict frame-range" IN and OUT parameters cannot be edited 2017-07-11 23:33:24 +12:00
blenderplayer fix: overlooked the RET_ZERO appendix 2017-06-25 17:04:47 +02:00
creator Remove MinGW support 2017-05-27 15:34:55 -04:00
gameengine Fix T51889: new file or load factory settings results in broken UI. 2017-07-08 00:54:05 +02:00
tools@b11375e890 Fix blurry icons 2017-01-29 17:21:57 +03:00
CMakeLists.txt