While I agree with you that providing a simple self-contained keyword describing a certain kind of "button" is great for those user that do have devices that provide exactly this functionality, I still vote for additionally having a "basic" (or fully definable) button keyword that handles all thinkable cases, and can be used by "experts" (to define configuration files, that nonetheless can be used by "anybody").
I already described this several weeks ago, but maybe the recent discussions might add some after thoughts to that.
It should be definable ho press and release are recognized, and what to do at press and at release-time of the button (what to send what CSI action should be fired).
As I described in that message, with this it would even be possible to create a pair of buttons from a rotary (e.g. to scroll the channels).
-Michael
|