Now that I think about it, its kind of similar to how it behaves when you click-n-drag a multiple selection of objects. Except there, the mouseup keeps the selection but does not activate the text for editing, which is good. But I think with a single object box, it should loose the selection if there was a click followed by a drag. click then mouseup should stay the same.

.hc

On Thu, 2011-09-15 at 15:21 -0400, Hans-Christoph Steiner wrote:

One thing that often bugs me when editing is the click-n-drag behavior of objects. Here's the outline:

click and release unselected object

• mouse down selects the object
• mouse up selects the text

click and release selected object

• mouse down drags the cursor in the text
• mouse up does nothing

click and drag unselected object

• mouse down moves the object
• mouse up releases the drag and selects the text

click and drag selected object

• mouse down moves the cursor in the text
• mouse up stops that

I think that a better behavior would be this. When an unselected object is click-n-dragged, mouseup doesn't select the text or the object. Then you can move an object, then immediately move it again without having to click to deselect it first.

This can be done with a 'moved' flag. But I can't really find where to put it, that code is pretty hard to follow (g_rtext.c, g_text.c, and the widgetbehavior). I attached my log of the pd-gui messages of the four cases above.

.hc