Page 1 of 1

annoyance : incorrect positioning of Audacity window

Posted: Mon Mar 16, 2009 1:59 am
by DaveKimble
This has been raised before as "Audacity start position under Windows XP" in 2007 but hasn't been fixed in v1.2.6.

With the wide screens we have these days, it makes sense to have the Windows Taskbar parked at the left edge of the screen, not the default bottom location.
Audacity doesn't recognise this and opens behind the taskbar. The fix suggested in the earlier thread assumes the taskbar is 10 pixels wide, which is wrong.
The width is whatever the user sets it as, and should be available to Audacity as some System.Form variable (guessing).

Maximising the window works OK, but Restoring puts the windows behind the taskbar again.

Dragging the window into the open works OK, and maximising-restoring remembers where it was dragged to, but File > Exit > doesn't save the new window position.

Dave

Re: annoyance : incorrect positioning of Audacity window

Posted: Mon Mar 16, 2009 11:06 am
by stearman65
Why not do a "hide windows taskbar" in control panel when you are using audacity, that way your windows task bar will only appear when you hover the mouse near it.?
Stearman65

Re: annoyance : incorrect positioning of Audacity window

Posted: Mon Mar 16, 2009 10:19 pm
by steve
DaveKimble wrote:This has been raised before as "Audacity start position under Windows XP" in 2007 but hasn't been fixed in v1.2.6.
It's not going to get fixed in Audacity 1.2.x either. Development of 1.2 ended some time ago. All current development is on 1.3 and is working toward the new "Audacity 1.4 stable".

In Audacity 1.3.x the windows position will be set to wherever it was last, or you can manually edit the audacity configuration file (audacity.cfg)

Code: Select all

[Window]
X=0
Y=24
Width=1024
Height=695
Maximized=1

Re: annoyance : incorrect positioning of Audacity window

Posted: Tue Mar 17, 2009 11:01 am
by waxcylinder
[quote="DaveKimble"]This has been raised before as "Audacity start position under Windows XP" in 2007 but hasn't been fixed in v1.2.6. /quote]
Dave,
the developers are not going to put effort into bug fixes like this for 1.2.6 - they are working hard on the late stages of 1.3 and trying to get it to a release version (1.4) - Have you tried 1.3.7? does this still give you the same behaviour? It may be that this is already fixed in 1.3

WC