Version: (using KDE 4.0.82) Because in such currently user has really two panels: version A and version B (with plasma widget). And there is no point in configuring version B, if she/he will end up with version A anyway. In other words -- respect WYSIWYG.
can you try to explain this one again? i don't quite understand what you are requesting in this one.
Ok, with with locked widgets you see the panel as you use it right -- everything is exact and in proper placed. Width, height, placement, everything. It is version A. Now you want to change some things, no matter what, but to do this you have to unlock the widgets (*). But when you do this, plasma widget appears. And now you don't have panel A, you have panel B. You don't configure panel A, but B. You cannot be sure how it will look like because you are looking at different object, so you have to guess. If user wants to _fine-tune_ his/her panel this is adding problems, because she/he has to make several iterations to really set everything up. Unlock -> change -> lock -> unlock -> change -> lock -> unlock -> change -> lock, ok, this time it looks like we wanted. (*) I don't think it is a good idea. Maybe it could be solved by letting to configure panels without unlocking widgets?
You might have been misunderstood because the "Plasma applet" you're refering to is called "cashew" in Plasma's terms.
Hello! This feature request 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 feature request is already implemented in Plasma 5, or is no longer applicable. Accordingly, we hope you understand why we must close this feature request. If the requested feature is still desired but not implemented 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