Version: (using KDE 4.2.2) Installed from: Ubuntu Packages On the systray notifier plasmoid, when you drag from the top instead of the sidebar, it orients it's top left corner to the mouse location, instead of where it was placed, regardless of mouse location on the top of the plasmoid. Sidebar did not stay attached to plasoid when dragging it around in this manner. Dragging works fin when dragging from the notifier's sidebar.
just so we can understand without ambiguity exactly what you mean, would it be possible for you to take a screenshot of the UI in question and label it with things like "top" and "sidebar" and whatever else might be useful to map your textual description to the actual GUI and then upload it as an attachment to this br? that would help avoid potential confusion.
Created attachment 33648 [details] Positioning the plasmoid. This is when positioning from the top of the plasmoid.
Created attachment 33649 [details] After the plasmoid has been placed. This is after I had released the mouse button. The cursor had not moved, but the plasmoid had.
Created attachment 33650 [details] Sidebar when attached to plasmoid.
The steps I took for these images are as follows (and the bug). I grab the plasmoid from the top region, holding down left click. I release the left mouse button. The plasmoid positions its top left corner to my mouse position, after release. Sorry for the confusion. Also I have only seen it happen on the file transfer plasmoid. I have not been able to try it on other notifications, and it does not happen with the desktop plasmoid. Need anything more, just let me know.
so two issues: 1) correct placement of the extender item under the mouse cursor while eing dragged and this is fixed in trunk 2) correct placement of the extender container applet when the extenedr item is dropped on desktop, and this will be more difficult (the mouse offset should be passed into the mime data?)
As item 1 is fixed already, I'm merging this with bug 198814, which describes item 2. Thanks *** This bug has been marked as a duplicate of bug 198814 ***