Re: Audacity 3.0.0 RC 006 for testing

On Wed, Mar 10, 2021 at 8:46 AM James Crook <[email protected]> wrote:

> The reason we don't show the RC number in the version number is that it
> would need to be removed when we release - and that would change the
> executable.
>
> We could though in future show a 'build number', and the higher the build
> number the more recent the RC.
>
> For VI users a quicker way of obtaining the build date and time is to
> click on help->check-for-updates
>
> That will open a browser, and the url it opens will be something like:
>
> https://www.audacityteam.org/download/?from_ver=3.0.0&Time=Mar9202110:29:46
>
> So you will get the time and date of the build.
>
> I agree about rearranging the build information tab.  It will help VI and
> normally sighted users alike.
>

Agreed - I only realized in the last six months or so (after 15 or so years
with Audacity)  that that
very useful information was available, but "hidden" down there.

Peter.



> --James.
>
>
>
> On Wed, 10 Mar 2021 at 01:34, Leland <[email protected]> wrote:
>
>> Unfortunately no.  The “RC” designation is simply a name we throw onto a
>> particular build and is not reflected in the app itself.
>>
>>
>>
>>
>>
>> *From:* Petr Pařízek via audacity-devel <
>> [email protected]>
>> *Sent:* Tuesday, March 9, 2021 7:22 PM
>> *To:* [email protected]
>> *Cc:* Petr Pařízek <[email protected]>
>> *Subject:* Re: [Audacity-devel] Audacity 3.0.0 RC 006 for testing
>>
>>
>>
>> Leland writes:
>> <<<<<
>> On the “Build Information” tab in Help -> About Audacity, you’ll find the
>> commit ID and date it was built near the bottom.
>> >>>>>
>>
>> Sure. But this doesn't tell me that it's RC06, does it?
>>
>> Petr
>>
>> P.S.:
>> I have to confirm David's words. While JAWS would normally load
>> HTML-style content into its own virtual buffer to allow a blind user to
>> read it linearly
>> (using what's called the virtual cursor), strangely enough, here it does
>> not. Therefore the only option is to first keep pressing either the down
>> arrow
>> key or Page Down until the final lines appear and then use the "Route
>> JAWS cursor to PC cursor" command and read the contents of the screen, line
>> by line,
>> by pressing the up or down arrow repeatedly. Unfortunately, I don't know
>> any details about how JAWS decides whether to load the content into its
>> virtual
>> buffer or not. So I can't probably be of much help in terms of knowing
>> what would have to be changed in that particular window in Audacity to make
>> it work
>>
>> as expected.
>>
>>
>>
>>
>>
>>
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>> Bez virů. www.avg.com
>> <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>>
>>
>> _______________________________________________
>> audacity-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>>
> _______________________________________________
> audacity-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/audacity-devel
>

_______________________________________________
audacity-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/audacity-devel