Re: Drag and drop patch for X, please review.

[Stefan Monnier <monnier@iro.umontreal.ca>]

> It is not a strict requirement.  There can be multiple pointer devices.
> In some accessibility functions you can simulate the mouse actions
> with arrow keys.

But if the source grabs the mouse, it is grabbed for all mice as well as for
those special arrow keys: i.e. there's still really only one pointer device
(which is a logical entity), just controlled from a bunch of different
hardware pieces (the mice and the keys).

>From the users point of view, there are several input devices that control
the cursor, but from the X clients, there's just only only cursor and they
don't care how the X server handles the hardware input devices to allow the
user to control the one and only cursor.

But it's still completely irrelevant to this discussion.

> The icon I am talking about is the one the user drags, i.e. it is
> where the pointer is.

Duh!  I finally understand, thank you.

> Then we are back to saying accept and then later perhaps signal
> an error.  I do not like that.  If we know we are going to raise an
> error, we should not accept the drop in the first place.

Well, we should still send a `reject' in the case where we know it will be
rejected (i.e. when there's no binding in the keymap), but if there's
a binding it's OK to say `accept' and later on signal an error.


        Stefan