Bug 1107 – Ergonomic order of Transport Toolbar gets unset

••• Introduction •••
••• Keywords •••

Audacity 3.0.3 development began 19th April 2021

Audacity Bugzilla

Bug 1107 - Ergonomic order of Transport Toolbar gets unset


Summary:	Ergonomic order of Transport Toolbar gets unset

Status:	CLOSED FIXED

Product:	Audacity
Classification:	Unclassified
Component:	User Interface
Version:	2.1.2
Hardware:	Per OS Windows 7

Importance:	P4 MoonPhase
Assigned To:	Default Assignee for New Bugs

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2015-08-01 10:16 UTC by Peter Sampson
Modified:	2018-08-20 11:45 UTC (History)
CC List:	8 users (show)

See Also:
Steps To Reproduce:
Release Note:
First Git SHA:
Group:	---
Workaround:
Closed:	2018-08-20 00:00:00

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Peter Sampson 2015-08-01 10:16:56 UTC

Occasionally when restarting Audacity I find that the Prefs setting for Ergonomic order of Transport Toolbar buttons gets unset.

This is very moonphase, it happened a fair bit in early 2.1.1 alphas and then seemed to go away in later 2.1.1 alphas and the release.  But today it happened again in 2.1.2 alpha.

All other Prefs settings seem to be retained ok when this happens.

W7-HP 64-bit 2.1.2 r3715b21 31-jul-15

Comment 1 Gale Andrews 2015-08-01 22:03:55 UTC

As soon as you restart Audacity and you notice that the toolbar and preference setting are incorrect, please attach audacity.cfg.

Comment 2 Peter Sampson 2016-01-14 10:01:17 UTC

Since reporting this earlier I have witnessed no instances of it happening again,
not with any of the current crop of RCs and recent alphas.

Comment 3 Peter Sampson 2016-05-09 08:31:23 UTC

This has not happened to me withe 2,1,2 or with any of the many alpha nightlies that I have been testing and using.

Comment 4 Gale Andrews 2016-05-14 14:07:40 UTC

(In reply to Peter Sampson from comment #3)
31 Jul 15 was the first wx3 build, which makes it sound like wx3 was the reason. 

But if you cannot reproduce it, please go ahead and close it WORKSFORME,

Comment 5 Peter Sampson 2016-05-16 04:07:19 UTC

WORKSFORME