From ad18c0fd55f17a49cc8b0d383254b7e89b89139b Mon Sep 17 00:00:00 2001 From: Benjamin Tissoires Date: Thu, 10 Sep 2015 16:10:03 -0400 Subject: [PATCH] TODO: add discussion regarding keys/macros Signed-off-by: Benjamin Tissoires --- TODO | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/TODO b/TODO index 2b91c730..e1e65edd 100644 --- a/TODO +++ b/TODO @@ -18,6 +18,15 @@ advantage we really get out of it is that a configuration UI would be able to update itself if a user presses a button to e.g. change the profile while the UI is running. +We should actually drop the "key" functionality in favor of macros: +- either a device supports real hardware macro, then there is no point in + having a special set of keys exported to the user space while the driver + can just figure out which way is most efficient +- if the device does not support macros, then all of the supported keys + should be RATBAG_SPECIAL, so the UI can enumerate them and get a capability + on the current button if it supports this particular action (example: + the UI is interested in sending "Volume Up", not KEY_VOLUMEUP. + Macro support: - enhance doctext - add API support for name/groups