This is an automatically generated e-mail. To reply, visit: http://svn.reviewboard.kde.org/r/5776/

On January 10th, 2011, 10 a.m., Kåre Särs wrote:

There is a problem with the new behavior for forced row count. 
Previously the "older" windows/buttons stayed at approximately the same place when new windows where opened/closed, but now more than half of the windows jump back and forth whenever a window is opened or closed. I made a longer explanation of my problem with the new behavior in the bug report that this patch tries to solve. 

Should I maybe re-open the report?

Regards,
  Kåre
each way has its strengths and its challenges. adding an option to swap between the two ways is not a good solution in this case, so we need to pick one. i'm also uninterested in having it flip-flop back and forth in implementation. the way it is currently in 4.6 seems to cover a number of user needs very well. can't please everyone, as they say.

- Aaron


On November 6th, 2010, 8:58 p.m., Ingomar Wesp wrote:

Review request for Plasma.
By Ingomar Wesp.

Updated Nov. 6, 2010, 8:58 p.m.

Description

This should fix <https://bugs.kde.org/show_bug.cgi?id=215231>, but frankly I don't understand why it was done this way in the first place...
Bugs: 215231

Diffs

  • /trunk/KDE/kdebase/workspace/plasma/desktop/applets/tasks/taskitemlayout.cpp (1190987)

View Diff

Screenshots

3 forced rows, 1-5 windows, trunk vs. patched