Bug 165789

Summary: hovering the panel when adding plasmoids does not show the correct "drop-state"
Product: [Unmaintained] plasma4 Reporter: S. Burmeister <sven.burmeister>
Component: generalAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: aseigo
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description S. Burmeister 2008-07-05 14:17:57 UTC
Version:            (using Devel)
Installed from:    Compiled sources
OS:                Linux

Open the add plasmoids window and drag the fuzzy clock to the panel. For this example we want to drop it on the right edge of the panel, i.e. on the right of the digi clock.

If you enter the panel at some point while dragging the plasmoids it will eventually show the "drop allowed" cursor yet change to "forbidden" and not give you any chance to drop it next to the digi clock.

In order to work around this buggy behaviour you have to move the mouse at the very top of the panel, and move down if you are past the digi clock. If you get the forbissen again, move the mouse up a tiny bit, while still staying on the panel.

If you are on the right of the digi-clock and could drop the fuzzy clock, move the mouse to the left and back to the same position you were allowed to drop it a second ago, you will get the forbidden again.

IMHO it would be a lot less annoying, if the panel would just drop the plasmoid on the left of the existing applet, if you release the mouse-button on the left half of the existing plasmoid and the other way around for the right half.
Comment 1 Beat Wolf 2008-07-13 23:37:45 UTC
what would actualy be cool, if when you drag and drop the applet to the panel, that the visuals are like the moving of the applets on the panel itself.
Comment 2 Aaron J. Seigo 2008-07-14 09:27:35 UTC
i have a somewhat working patch that does exactly what comment 1 suggests, but i didn't get it into releasable shape in time for 4.1 ... it's what i want to provide in 4.2, in any case.