Dragging an applet twice breaks melange

This should be fixed in revision 507. Can you confirm that?

I now can drag once, click off (this now selects the right application, not the applet window), and then drag again.
However, I can't drag an applet without first unfocusing the applet window.
Steps:
1. Open screenlets-daemon / melange.
2. Create an applet (I used SidebarUA and Slideshow).
3. Drag the applet somewhere.
4. After finishing that drag, drag it again to a new location.

Attached is what I get from running "melange -l 5 -o STDOUT > melangelog".

I loaded melange first (no other instance of screenlet-related stuff was open), then used screenlets-manager to start an instance of the Ruler screenlet.

The first drag worked fine, however, every drag after that failed.
The last drag was done by clicking down, *then* moving the mouse (as annotated).

I would suspect that the bug is in the focussing of the applet or the mouse pointer grabbing. (But I don't know gtk/gdk/melange well enough to work it out!)

Strange, I can't reproduce this exact thing (tried with Clock, Slideshow and Ruler), but I have another problem with dragging that could be related.
For me dragging works until I focus another window (e.g screenlets-manager). If I then try to drag a screenlet (directly, before focusing it first) sometimes it will work and sometimes (approx. 1 in 10 times) it won't. Screenlets manager looses focus which would indicate that melange window picked it up, but the screenlet stays in place.

Something I noticed today:
My dragging also doesn't work when I wait for the buttons (menu/close) to fully appear, then try dragging.

I tried this out, but cannot reproduce this bug.
I this still an issue?

Yes, there's still some weirdness. I'm marking this as crucial for 0.1.

I've fixed this bug for me in bzr revision 609 - does anyone still get weirdness using this revision?

I am happy to report that I no longer experience this problem.

The physics engine seems to be broken, but it shouldn't take to much effort to fix it.

Since everyone who had this problem has been fixed, I'm marking this as fixed.
Sorry about the physics engine, Natan - I thought it would be better to fix a high-importance issue properly, and worry about the physics engine later. You'll just have to find out where to put the bits of code for starting and finishing 'moves', and possibly correct the setting of 'self.dragged' and 'self.mouse_down'.

No problem.

I agree with you about the priorities, and I don't mind handling this myself some time this week.