[PATCH wayland v4] protocol: Add DnD actions

[Bill Spitzak]

I really do not like the idea that the compositor is responsible for
matching up modifiers with actions.

Still trying to figure out why the destination cannot pick one of the
actions, rather than the compositor doing this. If the modifiers are needed
then either the destination gets the modifiers, or the source gets them and
uses them to alter the list of offered actions.

My best guess is that you are having trouble emulating XDND. I think that
is a poor excuse for a non-optimal api however, and I really doubt it
cannot be worked around.

My overall opinion is that the destination needs a lot more control over
this to get a proper modern ui. The destination may want to show a preview
of what the drop will look like, which means the destination MUST be able
to control the cursor image. I don't care if this somehow violates any
principles of grab. It can revert to the cursor image from the source when
the destination refuses the drag.

The destination must also be able to pop up a menu of actions that the user
chooses from. Therefore it must be able to get the list from the source and
respond with a chosen one. The reason the destination must do this is
because the drop target may be ambiguous, and the destination needs to be
able to ask the user which to do. The user does not see any difference
between this and deciding whether move/copy needs to be done, so any api
that does not allow the user to select both simultaneously with a single
push is broken.

On Wed, Sep 30, 2015 at 4:02 PM, Michael Catanzaro <mcatanzaro at igalia.com>
wrote:

>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-devel/attachments/20151001/70cf1aa8/attachment.html>