Block a user
WIP: Refactor: Move code into new SEQ_retiming_reset function
95fd2b6b44
Fix: VSE: Overlap when using reset retiming on strip with effect strips
f4a4e7f77a
Fix: Reset retiming doesn't update effect strip and meta strip ranges
b9882fe4a6
Refactor: Move code into new SEQ_retiming_reset function
Fix: VSE: Memory leak in SEQ_retiming_data_clear
4468d242c4
Fix: VSE: Memory leak in SEQ_retiming_data_clear
41430ed4bd
Cleanup: Split strip foreground drawing function
7a6a2519c5
Refactor: SubdivCCG: Extract utility method for boundary calculation
7fea77992c
Fix: Sculpt: Restore transform symmetry clipping lost in refactor
39c334582b
Sculpt: Data oriented refactor for nearest vertex search
Fix: VSE: Moving a retiming key above a strip would cause overlapping
Yeah I agree, the code confused me as well. I think the issue is because of the if (selected)
before the else if(...)
statement for it. You can't transform an active non-selected strip, so…
Fix: VSE: Moving a retiming key above a strip would cause overlapping
This is another PR for #124332
303b01dddf
Much simpler implementation of #visible_strips_ordered_get
78db550b31
Draw ordering of the strips using Richard's code.
Fix: VSE: Moving a retiming key above a strip would cause overlapping
Testing it, I noticed that that doesn't work with dependent effect strips. Something like this would be very simple, though I'm not sure if it's too risky for this bug fix:
static void…
Fix: VSE: Moving a retiming key above a strip would cause overlapping
Something like this would work, but I am not proud of this code
I'd personally prefer having something like a strip_has_selected_retiming_keys
function and do it the same way it is done for…