diff options
author | Kristian Høgsberg <krh@bitplanet.net> | 2010-09-02 20:22:42 -0400 |
---|---|---|
committer | Kristian Høgsberg <krh@bitplanet.net> | 2010-09-02 20:22:42 -0400 |
commit | e9d37bdc5fe7f0244695859d5905af87dd3c82aa (patch) | |
tree | d3b8857fff9c735337fb655a352e63349e5d53e8 /TODO | |
parent | 5c63df7f1eafa8badf2290e9c732a1e890d983b5 (diff) |
Use a transient object for the dnd session
Diffstat (limited to 'TODO')
-rw-r--r-- | TODO | 24 |
1 files changed, 0 insertions, 24 deletions
@@ -27,18 +27,6 @@ Core wayland protocol send a NULL type or x-wayland/root-something type if the source offers that. - Races between pointer motion, ending the drag, the target sending - accept request and the source receiving the target event. - - - We've sent a drag focus or motion event to the source, but - haven't received an accept request corresponding to that event - and now the button is release. The compositor could wait for - the source to reply to outstanding focus/motion events before - sending the finish event to the source. Or we could send the - finish event through the source so that it needs to reply to the - 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? @@ -48,18 +36,6 @@ Core wayland protocol 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. - - 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 |