Lines Matching refs:button

3 Lws provides an GPIO button controller class, this centralizes handling a set of
6 intervals only when one or more button is down.
8 Each button has its own active level control and sophisticated state tracking;
9 each button can apply its own classification regime, to allow for different
10 physical button characteristics, if not overridden a default one is provided.
21 particular button.
24 the button is pulled-up, that's the downgoing edge only.  This avoids any
32 around the button causing drift and oscillation, the bottom-half briefly drives
33 the button signal to the active level, forcing a more deterministic charge level
39 is the engine of the rest of the classification while any button is down.  The
42 ## Declaring button controllers
44 An array of button map elements if provided first mapping at least GPIOs to
45 button names, and also optionally the classification regime for that button.
47 Then the button controller definition which points back to the button map.
74 That is all that is needed for init, button events will be issued on lws_smd
80 style and the characteristics of a particular type of button.
86 ms_up_settle|20ms|After the first indication a button is no longer down, the button is ignored for …
93 The button controller emits system messages of class `LWSSMDCL_INTERACTION`,
98 	"type":  "button",
99 	"src":   "controller-name/button-name",
104 For example, `{"type":"button","src":"bc/user","event":"doubleclick"}`
108 Using button names allows the same code to adapt to different hardware or
109 button mappings.  Button events may be synthesized for test or other purposes
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
129 the regime structure and the regime structure chosen per-button.
132 the button is doing, eg, a "click" event on a specific button.  Rather than
156 "stilldown" at intervals if the button is down long enough