Re: Proper representation of button touch (as opposed to button press)

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

Hi Jason,

On Fri, Mar 02, 2012 at 10:36:22AM -0800, Jason Gerecke wrote:
> The Intuos5 was just announced, and I'm working on adding support for
> it to the wacom kernel module. One feature new to the Intuos5 is the
> addition of capacitive sensors embedded in the buttons. Each
> ExpressKey (button) has two bits of state: one for the capacitive
> switch and one for the mechanical switch. These bits are synthesized
> into three cases: released, touched, and pressed (the 4th case of
> "pressed with a non-capacitive object" isn't particularly
> interesting). My initial thought was to call input_event() with a
> unique value for the 'touched' case. However, the documentation only
> defines three values for EV_KEY: 0 (released), 1 (pressed), and 2
> (autorepeat).
> 
> Is 'touched' a case we would want to allow for EV_KEY, or should I be
> representing things differently?

Differently please. It looks like you have 2 independent objects there -
one mechanical switch (persistent on/off) and one is a key (pressed
while touched).

Thanks.

-- 
Dmitry