From 9b2228d6fd7c72eb1bc0a97b5d2f4e9d1ae84231 Mon Sep 17 00:00:00 2001 From: Johannes Mueller Date: Tue, 7 Jul 2020 15:04:15 +0200 Subject: [PATCH] Fix ripple moving automation points When ripple moving a region all the subsequent regions will be moved, next region in the playlist after the dragged one first, last region of the playlist last. Thus, when an automation point is ripple moved along a region past the starting point of the next region, it will be moved again along with the next region as the move of the next region occurs after moving the automation point. This fix reverses the sequence of the ripple moves, last region in the playlist will be moved first, the next after the dragged one, last. So no temporary overlap of regions will occur. --- gtk2_ardour/editor_drag.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gtk2_ardour/editor_drag.cc b/gtk2_ardour/editor_drag.cc index 84e965a0bd..0bea5c18fa 100644 --- a/gtk2_ardour/editor_drag.cc +++ b/gtk2_ardour/editor_drag.cc @@ -2194,7 +2194,7 @@ RegionRippleDrag::add_all_after_to_views(TimeAxisView *tav, samplepos_t where, c } } - for (RegionSelection::iterator i = to_ripple.begin(); i != to_ripple.end(); ++i) { + for (RegionSelection::reverse_iterator i = to_ripple.rbegin(); i != to_ripple.rend(); ++i) { if (!exclude.contains (*i)) { // the selection has already been added to _views