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

From Audacity Wiki
Jump to: navigation, search
(The behavior varies depending on the command used and whether or not a selection exists.)
(added anchors - helps preserve spacing when editing)
Line 2: Line 2:
  
 
__NOTOC__
 
__NOTOC__
 
+
<div id="problem"></div>
 
==The Problem==
 
==The Problem==
 
Where new tracks are created has mostly been out of  the control of the user. Mostly these are placed at the end (bottom) of the project which may no be ideal particularly for users with large multi-track projects.
 
Where new tracks are created has mostly been out of  the control of the user. Mostly these are placed at the end (bottom) of the project which may no be ideal particularly for users with large multi-track projects.
Line 9: Line 9:
  
  
 +
<div id="feature"></div>
 
== Proposed Feature ==
 
== Proposed Feature ==
 
TBP
 
TBP
  
  
 +
<div id="backing"></div>
 
==Developer/QA Backing==
 
==Developer/QA Backing==
 
*'''Peter'''
 
*'''Peter'''
Line 23: Line 25:
  
  
 +
<div id="uses"></div>
 
==Use Cases==
 
==Use Cases==
 
TBP
 
TBP
  
  
 +
<div id="details"></div>
 
==Details==
 
==Details==
 
The behavior varies depending on the command used and whether or not a selection exists.
 
The behavior varies depending on the command used and whether or not a selection exists.
Line 50: Line 54:
  
  
 +
<div id="examples"></div>
 +
===GUI Examples===
 +
Not needed.
  
===GUI Examples===
 
TBP
 
  
 +
<div id="fr"></div>
 
==Previous Feature Requests relating to this proposal==
 
==Previous Feature Requests relating to this proposal==
 
TBP
 
TBP

Revision as of 12:34, 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

Where new tracks are created has mostly been out of the control of the user. Mostly these are placed at the end (bottom) of the project which may no be ideal particularly for users with large multi-track projects.

We have received Feature Requests from users who woulkd like to control where new tracks are placed in their project.


Proposed Feature

TBP


Developer/QA Backing

  • Peter
  • Steve wrote in the email discussion thread on the Quality list==Developer/QA Backing==
    • 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.
  • Robert (Accessibility)


Use Cases

TBP


Details

The behavior varies depending on the command used and whether or not a selection exists.

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

Focus

In all cases Focus should be transferred to the new track.


GUI Examples

Not needed.


Previous Feature Requests relating to this proposal

TBP