View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002787 | ardour | features | public | 2009-07-22 18:58 | 2009-08-31 20:08 |
Reporter | colinf | Assigned To | |||
Priority | low | Severity | feature | Reproducibility | N/A |
Status | acknowledged | Resolution | open | ||
Product Version | SVN/2.0-ongoing | ||||
Summary | 0002787: <Ctrl>+up/down appears to not move tracks over hidden tracks | ||||
Description | If you use <Ctrl>+up-arrow/down-arrow to move the selected track(s) up or down, and there are hidden tracks in the project, the selected track won't appear to move as it passes the position of the hidden tracks. You can see what's happening if the "Tracks/Busses' tab is visible in the Editor window: the tracks are being re-ordered, but because the selected track is moving past hidden tracks, its position in the main pane doesn't change. | ||||
Tags | No tags attached. | ||||
|
do you think this should really be changed? i find the current behaviour correct (although slightly unintuitive if you're not watching the track menu). and since this shortcut can be invoked everywhere, it's probably quite hard to make it behave differently depending on whether the user seems to be looking at the tracks or the track list. |
|
I do agree that the present behaviour is consistent, and anything different could be more tricky to implement. However, I was working on a project with many hidden tracks, interspersed with non-hidden ones, and it took me a long while to work out why <Ctrl>+up/down only seemed to move the selected track some of the time. If I hadn't happened to look at the "Tracks/Busses" tab, I would still be bemused. Usually, when I move a track up or down, it's because I want to look at that track and another one next to each other. In general, both those tracks will already be visible, and I don't care about any tracks that are hidden, so even once I'd worked out what was happening, it's not ideal. Anyway, it's not a big deal: it just caught me out. |
|
leaving this open as a feature request - maybe someone someday comes up with a good idea to solve this usability issue. |
Date Modified | Username | Field | Change |
---|---|---|---|
2009-07-22 18:58 | colinf | New Issue | |
2009-08-15 02:31 | nettings | Note Added: 0006536 | |
2009-08-15 02:31 | nettings | Status | new => feedback |
2009-08-25 13:39 | colinf | Note Added: 0006607 | |
2009-08-31 20:08 | nettings | cost | => 0.00 |
2009-08-31 20:08 | nettings | Note Added: 0006616 | |
2009-08-31 20:08 | nettings | Priority | normal => low |
2009-08-31 20:08 | nettings | Severity | trivial => feature |
2009-08-31 20:08 | nettings | Reproducibility | sometimes => N/A |
2009-08-31 20:08 | nettings | Status | feedback => acknowledged |
2009-08-31 20:08 | nettings | Category | bugs => features |