|Anonymous | Login | Signup for a new account||2017-09-24 03:26 PDT|
|My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0007214||ardour||bugs||public||2017-01-25 09:27||2017-09-21 04:43|
|Product Version||5.X git (version in description)|
|Target Version||Fixed in Version|
|Summary||0007214: Range selection drags de-select currently selected markers|
|Description||The marker selection is cleared ion starting a range selection drag, which I don't think should happen.|
|Tags||No tags attached.|
This is caused by the calls to selection->clear() in Editor::set_selected_track_as_side_effect().
I'm not sure what part of the selection those are meant to clear, but I don't think the marker selection needs to be cleared there.
|This is intentional, because the existence of multiple selections of different kinds of objects creates ambiguity when (for example) cut/copy/delete operations are used.|
I'm sure that marker and range selections used to be able to co-exist, and I found it a useful feature for editing, especially in conjunction with 'Playhead to active marker'.
It's useful to place and select a marker at a point where I want to make an edit, then scroll around, selet and copy the range I want to use, and then jump back to the selected marker to paste, and this is now broken.
I don't think there's any ambiguity with simultaneous marker and range selection anyway, since Cut, Delete, &c. don't apply to selected markers. If there were any ambiguity, it would apply equally well to simultaneous marker and region selections, which seem to be perfectly well allowed still.
|2017-01-25 09:27||colinf||New Issue|
|2017-03-24 10:25||colinf||Note Added: 0019554|
|2017-09-13 11:40||colinf||Relationship added||related to 0007474|
|2017-09-20 21:49||paul||Note Added: 0020026|
|2017-09-21 04:43||colinf||Note Added: 0020029|
|Copyright © 2000 - 2017 MantisBT Team|