summaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2012-06-13 13:33:01 -0400
committerKristian Høgsberg <krh@bitplanet.net>2012-06-13 13:33:01 -0400
commit6e94028c31d06999cb9848b1bd0348ea2f683516 (patch)
tree0412493b36d1f219869f34278ef7b6f87adce6a8 /TODO
parent8dc57f4dda804f50515a7a5366dceef13999ebcd (diff)
TODO: Update to account for changes from Daniel
Diffstat (limited to 'TODO')
-rw-r--r--TODO14
1 files changed, 0 insertions, 14 deletions
diff --git a/TODO b/TODO
index e6f290f..d09f785 100644
--- a/TODO
+++ b/TODO
@@ -27,20 +27,6 @@ Core wayland protocol
is something in the protocol/architecute that makes it harder than
it should be.
- - Key events need a bit more work/thinking/redesign. As it is we need
- a mechanism to change and synchronize keymaps, repeat rates. But
- as we started talking, we decided that we needed to go back and
- research what other systems do instead of just essentially copying
- the X model. Sending out unicode events in addition to keycode
- events has a lot of benefits (OSK can send out unicode events
- instead of fake keycode events, apps become much simpler...) Move
- keymap handling and repeat to the server? Needs more research.
-
- - Pointer axis events need modifiers (ctrl-scroll eg), but we either
- need to send the modifier state with each axis/scroll event or send
- keys down on pointer_focus and subsequent key events... or just key
- events for modifier keys... or for the non-repeating subset?
-
- Add timestamp to touch_cancel, add touch id to touch_cancel (?)
- The output protocol needs to send all the ugly timing details for the modes.