Graph Editor: Fcurve extrapolation visibility
Tweak option in Animation preferences to toggle off visibility of extrapolated f-curves ( those infinite lines before and after first and last keyframes on the f-curve). It will get a little bit less mess with f-curves in graph editor.
I suggest to place 'Show extrapolation' command with on/off checkbox in the graph editor menu - View.
The option ‘Show extrapolation” is ON by default. Graph editor behavior is as usual.
If the option ‘Show extrapolation” is OFF then:
- Constant extrapolations are hidden.
- Linear extrapolations are shown.
- Cycle modifier present but set to No Cycles: see above.
- Finite cycles are shown. Beyond the cycles: see above.
- Infinite cycles are shown.
Single keys. They should be shown just as single keyframes in the graph. I don't think it will be hard to find them because if you have keyframes then you have channels, so you can easily select channels you want then press 'View_all' hotkey
and for the single object/bone:
8 Comments
maybe slider for visibility? i would prefere to almost hide them, but at the same time being able to determine their existence at the second glance. That would be cool
this looks similar to this one. blender.community/c/rightclickselect/rhdbbc/
I think we should combine both ideas, if the visiblity option is on then the extrapolation should be in dashed lines & if Off then what you have suggested.
* @Pascal 0 * I don't see any reason to keep these lines half/dash visible. What for? In linear and cyclic types you these lines will be visible on those fcurves you need only, so there is no visual noise. But why you need to see em in constant type? for cycles? see above.
(removed after text was clarified)
(removed after text was clarified)
I thought about this too for a while and my assumption that those infinite lines were there because you can easily insert keys on the curves with ctrl+RMB.
Iif we can maintain that core feature with this changes then i think many of us will want it to be the default, it also would help if those inserted keys automatically snap to frames because right now they don't.
* @Cobra * those lines should be just invisible only, so I believe there will be no difference in fcurve behavior such as inserting keys with ctrl+RMB (LMB) and other
Agree, it can provide less visual noise but keep changes there, where they happened