Audacity Bug Summary
••• Introduction •••
••• Keywords •••
    Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla



Bug 562 - Win/Mac: Timer Record End Date Calendar prevents you going back to today
Win/Mac: Timer Record End Date Calendar prevents you going back to today
Status: CLOSED WORKSFORME
Product: Audacity
Classification: Unclassified
Component: User Interface
2.0.2
Other macOS and Linux
: P4 Repeatable
Assigned To: Vaughan Johnson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-07-23 18:03 UTC by Gale Andrews
Modified: 2018-08-20 11:51 UTC (History)
4 users (show)

See Also:
Steps To Reproduce:
1 Initialise .cfg if not already 2 Transport > Timer Record 3 Set End Date to tomorrow using the Calendar 4 Open End Date calendar again. Today is greyed out (but not hatched out) and cannot be selected. The only way to set the End Date back to today is to select a previous month.
Release Note:
First Git SHA:
Group: ---
Workaround:
Closed: 2018-08-20 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Gale Andrews 2012-07-23 18:03:09 UTC
Although this is only P4 in itself, while bug 561 exists this bug precludes any obvious way of changing the End Date back to today.
Comment 1 Vaughan Johnson 2012-07-26 21:27:34 UTC
See http://bugzilla.audacityteam.org/show_bug.cgi?id=561#c1.
Comment 2 Gale Andrews 2012-07-27 04:45:27 UTC
REOPENED. 

> http://bugzilla.audacityteam.org/show_bug.cgi?id=561#c1
I had already established that reverting r11636 did nothing for the this bug, which I think is long-standing. 

One effect that r11636 did have on Mac / Linux was that the "date picker" control became editable (you could type in it, which had the desired effect where the interdependence wasn't broken). But now having reverted 11636, Linux/Mac users cannot type in the date picker (which here is a text box, not a spin box), so they must use the calendar to change Start or End date.
Comment 3 Vaughan Johnson 2012-07-27 19:27:48 UTC
(In reply to comment #2)

> REOPENED. 

No need to put that in the comment when the status change is in the Bugzilla notice. No need to yell.


> 
>> http://bugzilla.audacityteam.org/show_bug.cgi?id=561#c1
> I had already established that reverting r11636 did nothing for the this bug,
> which I think is long-standing. 

That obviously wasn't clear to me. 


> 
> One effect that r11636 did have on Mac / Linux was [...]

If r11636 is irrelevant to this bug, it should not be discussed here, so I moved this thread to bug 561.
Comment 4 Gale Andrews 2012-07-28 03:26:36 UTC
(In reply to comment #3)
Hi, Vaughan. There was no yelling. I capitalise RESOLVED - FIXED too. :>)
Comment 5 Vaughan Johnson 2012-07-30 15:22:36 UTC
(In reply to comment #4)

;-))
Comment 6 Gale Andrews 2012-08-01 15:41:37 UTC
This may be a Wx bug and should be researched as such.
Comment 7 Peter Sampson 2017-10-25 14:08:56 UTC
Testing on RC1-4 on
a) W10 Home
b) macOS 10.13 High Sierra

Works for me on both platforms

If this was a Wx bug - it may well have been fixed by our wx upgrades