View Issue Details

IDProjectCategoryView StatusLast Update
0006019ardourfeaturespublic2020-04-19 20:16
Reportercolinf Assigned Tocolinf  
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Summary0006019: Behaviour of selected regions after splitting should be configurable
DescriptionFollowing a great deal of discussion on IRC and email, it seems that there's no single behaviour of what the subsequent selection should be when selected regions are split that's acceptable to everyone.

Thus, despite that there there are arguably already too many config options, a new one appears to be the only universally acceptable solution.

There are several possible behaviours that we might want to be able to select between, relating to both the newly-created regions and other selected regions, viz:

Of the regions newly-created by the split, the selection afterwards should include:
 (1) neither region
 (2) the region to the right of the split
 (3) the region to the left of the split
 (4) both regions

Other regions selected before the split operation but unaffected by it should:
 (a) be deselected
 (b) remain selected

There are thus eight possibilities. I personally see (1a) as being the most useful, and feel that (1b) is probably completely useless. Others definitely want some variant on (4), but since this is not a mode I'd use, I don't know whether (4a) or (4b) would be more useful, or whether offering the choice of one or the other would be worthwhile.

Also, would anybody ever need either variant of (2) or (3)?



Additional InformationI propose to implement this config option based on whatever anyone finds useful: I'd love to keep the number of options to a minimum (although definitely including (1a)), but can anyone who sees a need for any other of the eight modes above please add a comment here, and I'll add it to the possible choices.
TagsNo tags attached.

Activities

colinf

2014-11-18 19:48

updater   ~0015994

Implementation of this is now in select-after-split git branch.

colinf

2015-02-11 15:01

updater   ~0016340

Implemented in master branch in 18231264

system

2020-04-19 20:16

developer   ~0023337

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2014-10-30 18:24 colinf New Issue
2014-11-18 19:48 colinf Note Added: 0015994
2015-02-11 15:01 colinf Note Added: 0016340
2015-02-11 15:01 colinf Status new => resolved
2015-02-11 15:01 colinf Resolution open => fixed
2015-02-11 15:01 colinf Assigned To => colinf
2020-04-19 20:16 system Note Added: 0023337
2020-04-19 20:16 system Status resolved => closed