aboutsummaryrefslogtreecommitdiff
path: root/TODO
diff options
context:
space:
mode:
Diffstat (limited to 'TODO')
-rw-r--r--TODO28
1 files changed, 1 insertions, 27 deletions
diff --git a/TODO b/TODO
index 59d6891..5f5df00 100644
--- a/TODO
+++ b/TODO
@@ -1,14 +1,5 @@
==============================================================================
-= define generic event struct (probably Pd-ized input_event )
- something like:
-
-struct input_event {
- struct timeval time;
- t_int type;
- t_int code;
- t_int value;
-};
-
+= define generic event timestamp struct (probably Pd-ized input_event )
The question is whether the timeval is needed at all. Linux and Darwin
support it. Currently, I can only think of UPS PWR events actually using
@@ -22,10 +13,6 @@ timevals.
UsagePage
-Misc Input/Generic Desktop X == ev_rel/rel_x
-Button Input/Button #1 == ev_key/btn_left
-
-
LED UsagePage => ev_led
LED Usages == Linux ev_led codes
@@ -61,18 +48,6 @@ Darwin
==============================================================================
-= raw values vs. calibrated
-
-- relative axes should probably be raw data, since its pixel data, but then
- this causes problems with sensitivity across different mice. The mouse
- sensitivity would probably best translate as resolution, ie calibrated data,
- rather than sensitivity, ie raw data.
-
-- absolute axes should be calibrated, so that the same positions on different
- devices map to the same value
-
-
-==============================================================================
= pollfn for mouse-like devices
- determine whether using a pollfn is actually better than using a t_clock
@@ -83,7 +58,6 @@ Darwin
- this is probably unnecessary since the t_clock seems to run well at 1ms delay
-
==============================================================================
= function return values