Page MenuHome

VSE: `Frame All` inside metastrips uses meta range
ClosedPublic

Authored by Andrea Beconcini (beco) on Oct 23 2021, 6:36 PM.

Details

Summary

This commit fixes T90633, it changes the behavior of the Frame All
operation when the user is tabbed into a metastrip: instead of using
the global timeline's range, Frame All uses the current metastrip's
range.

Diff Detail

Repository
rB Blender

Event Timeline

Andrea Beconcini (beco) requested review of this revision.Oct 23 2021, 6:36 PM
Andrea Beconcini (beco) created this revision.
source/blender/editors/space_sequencer/sequencer_view.c
95–102

Here I called SEQ_timeline_init_boundbox for the "magic numbers" it uses for the y-axis (I wanted to avoid duplicating those 0.0 and 8.0 initial values and keep them in a single place instead).

Richard Antalik (ISS) added inline comments.
source/blender/editors/space_sequencer/sequencer_view.c
96–98

I would preffer getting active metastack and then just check if you get NULL instead of accessing Editing members directly.

This revision is now accepted and ready to land.Oct 25 2021, 6:46 AM