diff options
author | Johannes Mueller <github@johannes-mueller.org> | 2017-07-23 20:07:17 +0200 |
---|---|---|
committer | Robin Gareus <robin@gareus.org> | 2017-07-25 17:39:08 +0200 |
commit | 9bfe404b4e9f5bc1bbe11b4ef6fd9778a362d04c (patch) | |
tree | 5b586087aa2d7d123d10bc0bdb61ddc76747e7ae /libs/ardour/automation_control.cc | |
parent | 681ab5233097dbbf699c9ce6bcc0b76eaa8a59a3 (diff) |
Fix #6280 – region (first_frame()==0) selectable with SnapRegionBoundary
Issue #6280 states that when selecting ranges using SnapToRegionBoundary it's
not possible to select regions with first_frame() == 0. This is because
Playlist::find_next_region() does not consider region boundaries == pos but
only > pos. Thus it never considers pos == 0 to be a region boundary.
This solution tries to be as little invasive as possible without changing the
semantics of PlayList::find_next_region(). Therefore position 0 is added to the
region boundary cache if there's a region starting at position 0 in any track.
Diffstat (limited to 'libs/ardour/automation_control.cc')
0 files changed, 0 insertions, 0 deletions