Bug 171423 - Don't scale icons during resizing the folderview plasmoid
Summary: Don't scale icons during resizing the folderview plasmoid
Status: RESOLVED DUPLICATE of bug 164354
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-21 20:51 UTC by Stephan Kleine
Modified: 2008-12-08 16:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stephan Kleine 2008-09-21 20:51:58 UTC
Version:            (using Devel)
Compiler:          GCC 4.3 KDE4 from openSUSE 11.1 Beta1
OS:                Linux
Installed from:    Compiled sources

Currently, when one resizes a folderview plasmoid, its content gets scaled and repainted with the original scaling after the resizing is finished.

That not only looks pretty strange but is also kinda counter intuitive.

Please change it so it behaves like file managers do during resizing - as in don't scale the content but adapt the layout of the contained objects to the current size of the container on the fly and not only when the resizing is finished.
Comment 1 Jonathan Thomas 2008-12-07 19:45:22 UTC

*** This bug has been marked as a duplicate of bug 164354 ***
Comment 2 Stephan Kleine 2008-12-07 21:15:30 UTC
Sorry, but IMHO that is no duplicate.

In #164354 it is about resizing plasmoids and scaling the content seamlessly during resizing without repainting at the end.

Here it is specifically, and only, about the folderview plasmoid where content is scaled but shouldn't.

In other words, during changing the size of the folderview plasmoid, the content shouldn't be scaled at all but keep its original size - like it would behave if I would resize a konqueror window showing a couple of icons (only the available space extends but the icon size remains the same).
Comment 3 Aaron J. Seigo 2008-12-08 16:39:47 UTC
Stephan: this report and #164354 are exactly the same issue. Jonathan knew what he was doing when he closed this as a duplicate.

*** This bug has been marked as a duplicate of bug 164354 ***