Proposal: Rationalizing where new tracks are created to aid usability and consistency

Proposal pages help us get from feature requests into actual plans. This page is a proposal to rationalize where new tracks are created to aid usability and consistency.

Proposal pages are used on an ongoing basis by the Audacity development team and are open to edits from visitors to the wiki. They are a good way to get community feedback on a proposal.

• Note: Proposals for Google Summer of Code projects are significantly different in structure, are submitted via Google's web app and may or may not have a corresponding proposal page.

The Problem

TBP

Proposed Feature

TBP

Developer/QA Backing

TBP

Use Cases

TBP

Details

I'd be happy with "Add track" adding a track below the track that has focus, if the behaviour is the same with other actions where:

1. One or more tracks are added.
2. The action does NOT act on and is NOT affected by selected audio.

These commands should create the new track after the currently focused track

The behaviour would thus be the same for:

• Add ... Track
• Generate > ... when there is no selection
• Analyze > ... when no label track is selected
• Record New Track
• Append record when there are insufficient track channels selected
• Detect upstream dropouts

These commands should create the new track after the last (bottom-most) selected track

but would NOT apply to actions that require a track selection. In these cases the commands act on the selection and indifferent to where focus happens to be, so I would expect the new tracks to be relative to the selection.

• Mix and Render
• Mix and Render to New Track
• Duplicate
• Split New

GUI Examples

TBP

Previous Feature Requests relating to this proposal

TBP