summaryrefslogtreecommitdiffstats
path: root/TODO
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2010-08-19 17:26:02 -0400
committerKristian Høgsberg <krh@bitplanet.net>2010-08-19 17:26:02 -0400
commit506e20eed96e39737a402358e43aa3d5249d49a0 (patch)
tree918391bd74e510421ba5183b953fb521cefd72e9 /TODO
parentAdd clean target for data/ so make clean works again (diff)
downloadwayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar.gz
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar.bz2
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar.lz
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar.xz
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.tar.zst
wayland-506e20eed96e39737a402358e43aa3d5249d49a0.zip
More work on dnd
Diffstat (limited to 'TODO')
-rw-r--r--TODO13
1 files changed, 13 insertions, 0 deletions
diff --git a/TODO b/TODO
index 5cb6ab4..601a97e 100644
--- a/TODO
+++ b/TODO
@@ -50,6 +50,19 @@ Core wayland protocol
finish event too. Either way, the state of the drag blocks on
the client. What if we drag to a client that doesn't doo dnd?
+ How do we animate the drag icon back to the drag origin in case of
+ a failed drag?
+
+ How to handle surfaces from clients that don't know about dnd or
+ don't care? Maybe the dnd object should have a
+ dnd.register_surface() method so clients can opt-in the surfaces
+ that will participate in dnd. Or just assume client is not
+ participating until we receive an accept request.
+
+ May need to look at all offer events before we can decide which one
+ to go with. Problem is, we don't know when we've seen that last
+ offer event.
+
- copy-n-paste, store data in server (only one mime-type available)
or do X style (content mime-type negotiation, but data goes away
when client quits).