Version: unspecified (using KDE 4.5.80) OS: Linux The positioning of applets is hard at grouping panel with flow group because you cant see exactly the size of the applet. There is only a gray block which nearly marks the postion where it will be inserted. That is bad. Try out how easy adding/moving applets at kde3 kicker was: - moving applets only possible if right click - move or (much easier) hold middle mouse button down and move applet. - the size of applet will be exactly show because you move the applet and it will be drawn during moving! - there is no requirement to lock applets manually, there always locked (except the case before) The kde4 panel applet add/move is really not user friendly yet :( You can try it simply with a virtual machine virtualbox, qemu/kvm with trinity kde3 image (any kde3 live cd fit too, e.g. kubuntu 8.04): http://mirror.its.uidaho.edu/pub/trinity/cdimages/kubuntu/maverick/kubuntu-10.10-trinity-enterprise-i386.iso Reproducible: Always
Closing for lack of feedback. Please feel free to reopen this report if you can still reproduce this with KDE 4.8.3 or later.
Still in bad state on 4.10rc3
curennt problems (4.10rc3): - applets not locked if the options not open - spacers cant be added - new row is always created below existing row - applets are lost the positions/size if the edge was changed It would be nice if these issues are corrected.
I have this problem as well. I have to trick some widget icons by moving the widget around them to prevent these icons from shrinking to a pixel size icon, rendering them invisible.
Hello! This bug report was filed for KDE Plasma 4, which reached end-of-support status in August 2015. KDE Plasma 5's desktop shell has been almost completely rewritten for better performance and usability, so it is likely that this bug is already resolved in Plasma 5. Accordingly, we hope you understand why we must close this bug report. If the issue described here is still present in KDE Plasma 5.12 or later, please feel free to open a new ticket in the "plasmashell" product after reading https://community.kde.org/Get_Involved/Bug_Reporting If you would like to get involved in KDE's bug triaging effort so that future mass bug closes like this are less likely, please read https://community.kde.org/Get_Involved#Bug_Triaging Thanks for your understanding! Nate Graham