In computer programming, an event handler is an asynchronous callback subroutine that handles inputs received in a program (called a listener in Java). Each event is a piece of application-level information from the underlying framework, typically the GUI toolkit. GUI events include key presses, mouse movement, action selections, and timers expiring. On a lower level, events can represent availability of new data for reading a file or network stream. Event handlers are a central concept in event-driven programming.
The events are created by the framework based on interpreting lower-level inputs, which may be lower-level events themselves. For example, mouse movements and clicks are interpreted as menu selections. The events initially originate from actions on the operating system level, such as interrupts generated by hardware devices, software interrupt instructions, or state changes in polling. On this level, interrupt handlers and signal handlers correspond to event handlers.
Created events are first processed by an event dispatcher within the framework. It typically manages the associations between events and event handlers, and may queue event handlers or events for later processing. Event dispatchers may call event handlers directly, or wait for events to be dequeued with information about the handler to be executed.
Read more about this topic: Event (computing)
Famous quotes containing the word event:
“We can glut ourselves with how-to-raise children information . . . strive to become more mature and aware but none of this will spare us from the . . . inevitability that some of the time we are going to fail our children. Because there is a big gap between knowing and doing. Because mature, aware people are imperfect too. Or because some current event in our life may so absorb or depress us that when our children need us we cannot come through.”
—Judith Viorst (20th century)