summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2010-08-24 17:34:15 -0400
committerKristian Høgsberg <krh@bitplanet.net>2010-08-24 17:34:15 -0400
commitd6a4787ed71136eac2894fd72f7dac7fc4fb6fab (patch)
tree111217a3734a9c224fa532caff196e2368436539
parent506e20eed96e39737a402358e43aa3d5249d49a0 (diff)
TODO editing
-rw-r--r--TODO17
1 files changed, 15 insertions, 2 deletions
diff --git a/TODO b/TODO
index 601a97e..49fe190 100644
--- a/TODO
+++ b/TODO
@@ -63,12 +63,25 @@ Core wayland protocol
to go with. Problem is, we don't know when we've seen that last
offer event.
+ Create transient dnd object when a client starts a drag. Announce
+ the dnd object to clients first time the drag enters one of its
+ surfaces. Track if we've already announced the object by comparing
+ the drag start timestamp/serial with the clients last-event
+ timestamp/serial? Wont work if we send other events to a client
+ after creating the drag object. Maybe just keep the transient
+ object on the initiator side?
+
+ - Pointer image issue:
+
+ - A touch input device doesn't have a pointer; indicate that
+ somehow.
+
+ - Cursor themes
+
- 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).
- - Optional pointer images.
-
- Discard buffer, as in "wayland discarded your buffer, it's no
longer visible, you can stop updating it now.", reattach, as in "oh
hey, I'm about to show your buffer that I threw away, what was it