summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKristian Høgsberg <krh@bitplanet.net>2012-05-08 14:49:44 -0400
committerKristian Høgsberg <krh@bitplanet.net>2012-05-08 14:49:44 -0400
commit6b8816bab46172abc975674dcefadcea4edcef08 (patch)
tree0ae535a65f14233c6a47c99ea82fbbcc7e17e6cf
parent0c20496e1ad16a2910b6f6c7afcf3f5a168f2436 (diff)
Update TODO
Daniel did fixed point coordinates.
-rw-r--r--TODO8
1 files changed, 0 insertions, 8 deletions
diff --git a/TODO b/TODO
index 2d6885f..f761a3b 100644
--- a/TODO
+++ b/TODO
@@ -27,14 +27,6 @@ Core wayland protocol
is something in the protocol/architecute that makes it harder than
it should be.
- - Reconsider data types for coordinates in events. double, floats or
- fixed point. Transformed and/or accelerated input generates
- sub-pixel positions. 24.8 fixed point could work. Need to think
- about the range of coordinates we need. Different from X problem,
- since we don't have sub-windows, which is where X hits the 16 bit
- limitations. Monitor and window sizes haven't yet out-grown the 16
- bit range.
-
- 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