Bugzilla – Bug 2405
Resizable toolbars when undocked and oversized get truncated on re-docking (not Time toolbar)
Last modified: 2021-02-15 14:02:11 UTC
If you resize an undocked meter toolbar wider than the Audacity window and then re-dock it the meter will be truncated on the right. This is not a regression we have had this since 1,3,2 when we first had re-dockable floated toolbars. Affects both meter toolbars - and in earlier Audacities affected the unitary meter toolbar that we had Same on both Win and Mac - so assume all platforms
This also affects the Device toolbar It dos not affect the ne Time toolbar
(In reply to Peter Sampson from comment #1) >It does not affect the ne Time toolbar Curiously if you dock it when it's oversized for the Window Audacity shrinks it to fit, but if you drag it to float it again Audacity restores the oversized size.
This also affects the Play-at-Speed toolbar - so affects all (older) resizable toolbars. It does not affect the new Time toolbars as, presumably, different more sophisticated code was used to handle it's resizing (in dealing with all the buggy quirks that we encountered while QA testing this new toolbar.
Is this really a problem? Try this: 1) Maximize the Audacity window 2) Reset toolbars 3) Resize the device toolbar to maximum width 4) Resize the Audacity window to something smaller Now look at the device toolbar. It's truncated. How is that any different than if we were to redock an overly wide toolbar? Here's a scenario that might irritate users... 1) User floats the recording meter 2) User starts recording 3) User resizes the Audacity window to get at something behind it 4) User redocks the recording meter 5) User maximizes the Audacity window If we implement an automatic resize for this bug, then the user will now have to resize the meter get things back the way he had them because we reduced the size of the toolbar at step 4.
(In reply to Leland Lucius from comment #4) Leland that second use-case is a *compelling* argument for this to be regarded as a "feature" and not a "bug" Accordingly I shall therefore close this as NOTABUG Apart from any other consideration I do not recall any user complaints about this - just QA being picky - as we are wont to do ;-)
