Not sure if this is a "technical issue" or other, but...
I'm wondering about the rationale for Pd's UI behavior when dragging an object on the canvas.
As I see it, there are two things you want the mouse to do with an object: edit its contents, or move it. These are separate use cases: when you're editing an object, you're not moving it; when you're moving an object, you're probably not interested in editing it.
The Pd interface actually blends these separate use cases in an awkward way: dragging an object on the canvas, when you release the mouse button, the object enters text-editing mode!
Does anybody actually want or like this behavior?
Is there any precedent, anywhere, in any other point-click GUIs for this?
Common user-interaction case: Use the mouse to pull the object close to where it should go, and then nudge by arrow keys for precise positioning. But arrow keys in fact move a text cursor through the box's content. To execute this arguably most-common object-positioning action requires an extra step in the middle: drag; rectangle-select the object (which was already selected, when you dragged it!); arrow-key nudge. Multiply by hundreds of times in a session.
If there is a concrete reason for this behavior that I'm overlooking, I'd like to know what it is.