Lines Matching +full:- +full:- +full:classification

5 one for interrupt to bottom-half event triggering and another that runs at 5ms
9 each button can apply its own classification regime, to allow for different
20 internal struct passed per-interrupt to differentiate them and bind them to a
23 The interrupt is set for notification of the active-going edge, usually if
24 the button is pulled-up, that's the downgoing edge only.  This avoids any
28 An OS timer is used to schedule a bottom-half handler outside of interrupt
31 To combat commonly-seen partial charging of the actual and parasitic network
32 around the button causing drift and oscillation, the bottom-half briefly drives
38 The bottom-half makes sure a monitoring timer is enabled, by refcount.  This
39 is the engine of the rest of the classification while any button is down.  The
45 button names, and also optionally the classification regime for that button.
79 The classification regime is designed to reflect both the user interaction
83 ---|---|---
85 ms_min_down_longpress|300ms|Down events longer than this are reported as a long-click
87 ms_doubleclick_grace|120ms|The time allowed after a click to see if a second, double-click, is fort…
99 	"src":   "controller-name/button-name",
100 	"event": "event-name"
106 JSON is used because it is maintainable, extensible, self-documenting and does
107 not require a central, fragile-against-versioning specification of mappings.
115 more typically the user code wants to consume a higher-level classification of
116 the interaction, eg, that it can be understood as a single "double-click" event. 
119 ---|---
120 down|The button passes a filter for being down, useful for duration-based response
122 up|The button has come up, useful for duration-based response
123 click|The button activity resulted in a classification as a single-click
124 longclick|The button activity resulted in a classification as a long-click
125 doubleclick|The button activity resulted in a classification as a double-click
127 Since double-click detection requires delaying click reporting until it becomes
128 clear a second click isn't coming, it is enabled as a possible classification in
129 the regime structure and the regime structure chosen per-button.
131 Typically user code is interested in, eg, a high level classification of what
147 ### Relationship between up / down and classification
149 Classification|Sequencing
150 ---|---
151 click|down-up-click (it's classified when it went up and cannot be a longclick)
152 longclick|down-longclick-up (it's classified while still down)
153 doubleclick|down-up-down-doubleclick-up (classified as soon as second click down long enough)