Difference between revisions of "Proposal: Rationalizing where new tracks are created to aid usability and consistency"

From Audacity Wiki
Jump to: navigation, search
({{Proposal_Header|This page is a proposal to rationalize where new tracks are created to aid usability and consistency. |}})
(Details)
Line 20: Line 20:
  
 
==Details==
 
==Details==
TBP
+
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:
 +
# One or more tracks are added.
 +
# 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 ... tracks
 +
* Generate menu > ... when there is no selection.
 +
* Analyze menu > ... when no label track is selected.
 +
* Record to new.
 +
* 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===
 
===GUI Examples===
 
TBP
 
TBP
 
  
 
==Previous Feature Requests relating to this proposal==
 
==Previous Feature Requests relating to this proposal==

Revision as of 12:02, 4 March 2020

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 ... tracks
  • Generate menu > ... when there is no selection.
  • Analyze menu > ... when no label track is selected.
  • Record to new.
  • 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