View Issue Details

IDProjectCategoryView StatusLast Update
0003168ardourfeaturespublic2020-04-19 20:14
Reporterdanboid Assigned Tocth103  
PrioritynormalSeveritytweakReproducibilityN/A
Status closedResolutionwon't fix 
Summary0003168: Amalgamate the three 'Select/Move' icons
DescriptionI've just been asking in #ardour why Ardour has 'Select/Move objects', Select/Move objects or ranges' as well as 'Select/Move ranges' icons instead of just one 'Select/Move' icon but no-one came forth with a reason.

If this has some sound design principals underlying it that are escaping me, please explain. Otherwise lets junk 'em in favour of just keeping the pointy hand icon as our universal Select/Move switch and cut out lots of confusion- at least for the MIDI editor.
TagsNo tags attached.

Activities

paul

2010-05-24 14:42

administrator   ~0007999

the distinction between objects and ranges from ProTools and has many ardent fans. there are several threads on GearSlutz for example that explore the power of these two editing modes, and talk about the power of linking and then separating them. so yes, you're missing some fairly fundamental sound design/audio editing principles, at least in as much as they affect the workflow used by many ProTools users.

range mode should (and will) play no role in MIDI data editing. that's why its taken over by the "draw notes" icon when editing MIDI items. its exclusion is not yet complete, however.

danboid

2010-05-24 19:09

reporter   ~0008006

Hi Paul!

OK- just wanted to hear the reasoning behind this. I suppose it could've remained as a request if entitled "Amalgamate the three 'Select/Move' icons in MIDI editing mode" but as it stands I suppose this can be resolved now.

cth103

2010-05-25 00:28

administrator   ~0008014

Marking this as resolved. Once the PT-style modes have been fully sorted out I guess there might be room for improvement here.

system

2020-04-19 20:14

developer   ~0022082

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
2010-05-23 15:52 danboid New Issue
2010-05-24 14:42 paul Note Added: 0007999
2010-05-24 19:09 danboid Note Added: 0008006
2010-05-25 00:28 cth103 cost => 0.00
2010-05-25 00:28 cth103 Note Added: 0008014
2010-05-25 00:28 cth103 Status new => resolved
2010-05-25 00:28 cth103 Resolution open => won't fix
2010-05-25 00:28 cth103 Assigned To => cth103
2020-04-19 20:14 system Note Added: 0022082
2020-04-19 20:14 system Status resolved => closed