diff options
| author | Kristian Høgsberg <krh@bitplanet.net> | 2012-05-08 14:49:44 -0400 |
|---|---|---|
| committer | Kristian Høgsberg <krh@bitplanet.net> | 2012-05-08 14:49:44 -0400 |
| commit | 6b8816bab46172abc975674dcefadcea4edcef08 (patch) | |
| tree | 0ae535a65f14233c6a47c99ea82fbbcc7e17e6cf /TODO | |
| parent | Input: Convert pointer co-ordinates to signed_24_8 (diff) | |
| download | wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar.gz wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar.bz2 wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar.lz wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar.xz wayland-6b8816bab46172abc975674dcefadcea4edcef08.tar.zst wayland-6b8816bab46172abc975674dcefadcea4edcef08.zip | |
Update TODO
Daniel did fixed point coordinates.
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 8 |
1 files changed, 0 insertions, 8 deletions
@@ -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 |