From e12059711346f72f73cb3595548f75d88aef56d1 Mon Sep 17 00:00:00 2001 From: Hans-Christoph Steiner Date: Sun, 7 Nov 2004 16:28:25 +0000 Subject: cleaned up the code a fair amount, but there are still lots of bugs bugs bugs... svn path=/trunk/externals/hcs/hid/; revision=2238 --- TODO | 28 +--------------------------- 1 file changed, 1 insertion(+), 27 deletions(-) (limited to 'TODO') 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 @@ -60,18 +47,6 @@ Darwin implemented -============================================================================== -= 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 @@ -83,7 +58,6 @@ Darwin - this is probably unnecessary since the t_clock seems to run well at 1ms delay - ============================================================================== = function return values -- cgit v1.2.1