Page MenuHome

Fix T43898: Sequencer - Ctrl snapping a sequencer strip does not work if you specify the x axis
AbandonedPublic

Authored by Bastien Montagne (mont29) on Mar 14 2015, 11:47 AM.

Details

Summary

As title says…

Also makes code a bit better “confined” I think (all snapping cooking is done inside the single snapSequenceBounds).
Now, this is still a bit hackish, especially how we 'disable' increment snapping when constrained, think the best thing would be to create a real seq snapping mode (would also allow to chose between snap to strips of incremental snap!).

Antony, not sure about what we want here…

Diff Detail

Event Timeline

Bastien Montagne (mont29) retitled this revision from to Fix T43898: Sequencer - Ctrl snapping a sequencer strip does not work if you specify the x axis.
Bastien Montagne (mont29) updated this object.
Bastien Montagne (mont29) set the repository for this revision to rB Blender.

The patch is not so good, application will not be done to all strips, only the first. This is coded in a way so that selected strips keep their offset in the selection

Just moving

snap_frame = snapSequenceBounds(t, mval);

before the CON_APPLY check, works here...I didn't understand what was the issue with that, ie which value is snapped to the grid?

It would be good to allow snapping to frames - or seconds too at some point but this is more a TODO than a fix.