Created attachment 69371 [details] With Folder View in panel - icons are clipped I just updated from KDE 4.8 to 4.8.1. Previously in 4.8 every icon and applet in the panel would scale correctly if I resized the panel. Now in 4.8.1 all the icons refuse to scale down at a certain point if the Folder View applet is present in the panel (in my attachment the folder view applet is in the top panel, 2nd icon from the left. After removing the folder view applet from the panel everything scales correctly...add it back and the scaling problem returns. One or both of the following commits may be the culprit: http://commits.kde.org/kde-baseapps/89208d71a9b0a3692ddec5218144beeafd7844e3 http://commits.kde.org/kde-baseapps/a8694a6d733f9fc8f1a08256826d65a6bef1720b
I will also note that this issue affects my desktop at work and my laptop at home. The desktop is running an ATI Radeon using built-in kernel drivers (v3.2.8) and the laptop is running an Nvidia with proprietary drivers (v295.20).
*** Bug 295562 has been marked as a duplicate of this bug. ***
Git commit 4327bca4915d30e194120aaa0b0cf48264a74428 by Ignat Semenov. Committed on 12/03/2012 at 20:50. Pushed by isemenov into branch 'master'. scale correctly when placed in a panel 1)Use setPreferredSize instead of setMinimumSize 2)Set the size policy to QSizePolicy::Minimum Also, remove update() from constraintesEvent() as per the docs. FIXED-IN:4.8.2 M +3 -4 plasma/applets/folderview/folderview.cpp http://commits.kde.org/kde-baseapps/4327bca4915d30e194120aaa0b0cf48264a74428
Git commit 43eb58c013fcb0bffbdf0d482c4284883366a597 by Ignat Semenov. Committed on 12/03/2012 at 20:50. Pushed by isemenov into branch 'KDE/4.8'. scale correctly when placed in a panel 1)Use setPreferredSize instead of setMinimumSize 2)Set the size policy to QSizePolicy::Minimum Also, remove update() from constraintesEvent() as per the docs. FIXED-IN:4.8.2 M +3 -4 plasma/applets/folderview/folderview.cpp http://commits.kde.org/kde-baseapps/43eb58c013fcb0bffbdf0d482c4284883366a597
*** Bug 296279 has been marked as a duplicate of this bug. ***