Testing needed for Layout fixes

Jakob Kummerow jakob.kummerow at googlemail.com
Wed Nov 11 00:58:47 CET 2009


Hi everyone, especially Nikolaj,

I've been asked to sum up today's testing results as collected on IRC:

Apparently when restoring, Amarok now returns to the layout it had
when the application *started*, not to the one it had before being
maximized (test: open Amarok, change the width of, say, the playlist
-> maximize Amarok -> restore Amarok -> playlist will have the width
it had initially).

Here's a proposal, not sure how much work it would be, i.e. whether
this would present a suitable last-minute fix for 2.2.1: Just remember
the relative sizes of all parts, for example if the Sources browser
had 20%, the CV 50% and the playlist 30% of the width before
maximizing, they will again have 20%, 50% and 30%, respectively, while
Amarok is maximized, and again after being restored. Same for manual
resizing of the window. AFAIK that is actually the default behaviour
of Qt widgets, so hopefully it's easy to implement :)

(Probably related to that: right now, dragging the splitters between
Sources/CV and CV/playlist behaves differently; and when maximizing,
the three columns react differently to the added total width, which is
a bit inconsistent.)

Lydia has not tagged 2.2.1 yet in order to give you a chance to look
at the layout again.

Hope I haven't forgotten anything.

Cheers,
Jakob


More information about the Amarok-devel mailing list