Difference between revisions of "Proposal Improvements to the Timer Record time data-entry spinbox controls"

From Audacity Wiki
Jump to: navigation, search
({{Proposal_Header|This page is a proposal for improvements to the time data-entry spinbox controls in Timer Record|}})
(((note|'''Peter 08Oct21:''' This is now logged on Github: [https://github.com/audacity/audacity/issues/1869 The Timer Record TimeText controls do not interact intuitively with the Date controls. 1869])
Line 1: Line 1:
 +
((note|'''Peter 08Oct21:''' This is now logged on Github: [https://github.com/audacity/audacity/issues/1869 The Timer Record TimeText controls do not interact intuitively with the Date controls. 1869]
 +
 
{{Proposal_Header|This page is a proposal for improvements to the time data-entry spinbox controls in Timer Record|}}
 
{{Proposal_Header|This page is a proposal for improvements to the time data-entry spinbox controls in Timer Record|}}
 
__NOTOC__
 
__NOTOC__

Revision as of 13:31, 8 October 2021

((note|Peter 08Oct21: This is now logged on Github: The Timer Record TimeText controls do not interact intuitively with the Date controls. 1869

Proposal pages help us get from feature requests into actual plans. This page is a proposal for improvements to the time data-entry spinbox controls in Timer Record
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 Problems

The Timer Record TimeText controls do not interact intuitively with the Date controls.

Proposed Features

  1. Improvements to the time data-entry spinner controls.

Developer/QA Backing

  • Peter Sampson:

Use Cases

  1. Users find the spinner data-entry for time values to be confusing and un-natural, causing incorrect entry values.

Details

Improvements to the time data-entry spinbox controls

  • Simplified spinner controls for time entry with hh:mm only (I doubt that anyone uses seconds except when testing).
  • hh (and mm) to be a single field rather than separate digits of units and tens. Thus the up/down arrows would operate on hh (and mm) as an entity.
  • No ripple-through interaction from the hours field to the date field.
  • No ripple-through interaction from the minutes field to the hours field.
  • The minutes field to be limited to its logical maximum of 59 minutes.
  • The hours field to be limited to its logical maximum of 23 hours.
    • Gale: There are at least two cases where the Start and End spinboxes interact unintuitively with Date:
      • You cannot type a spinbox character that results in a time in the past; the input is ignored and the selected digit is advanced. In particular there is a clearly expressed expectation that setting hours to the past would advance the date forwards.
      • The hour spinbox increments the date perfectly in a forwards direction by typing or up arrow (even incrementing by a day and changing hours to "07" if you have 21 hours and increment the "2" to "3"). However incrementing hours backwards with down arrow does not move the date backwards when you reach "00" hours (even if the previous day would still be a time in the future); moreover a further down arrow from "00" hours zeroes all the digits.
      • The above are not apparently bugs but arguably reasonable behaviour for TimeText controls as used in Selection Toolbar. Perhaps these are not good behaviours in a Timer and may suggest using another type of control integrated with the date. Or perhaps time controls should increment date backwards and a time in the past can be set, but it greys out OK.


GUI Examples

TBP