Lines Matching refs:events

7 The event loop library allows components to declare events to which other components can register h…
8 execute when those events occur. This allows loosely coupled components to attach desired behavior …
9 …nvolvement. For instance, a high level connection handling library may subscribe to events produced
10 by the wifi subsystem directly and act on those events. This also simplifies event processing by se…
16 There are two objects of concern for users of this library: events and event loops.
19 …g a two part identifier which are discussed more :ref:`here <esp-event-declaring-defining-events>`.
20 Event loops are the vehicle by which events get posted by event sources and handled by event handle…
65 …      // 4. Post events to the loop. This queues the event on the event loop. At some point in time
82 .. _esp-event-declaring-defining-events:
84 Declaring and defining events
87 As mentioned previously, events consists of two-part identifers: the event base and the event ID. T…
88 of events; the event ID identifies the event within that group. Think of the event base and event I…
107 …e base identifiers for system events are uppercase and are postfixed with ``_EVENT``. For example,…
129 The default event loop is a special type of loop used for system events (WiFi events, for example).…
130 …the user. The creation, deletion, handler registration/unregistration and posting of events is done
151 Other than the API difference and the special designation to which system events are posted to, the…
152 …ult event loops and user event loops behave. It is even possible for users to post their own events
160 It is possible to register a single handler to multiple events individually, i.e. using multiple ca…
163 …t is desirable for a handler to execute on (1) all events that get posted to a loop or (2) all eve…