Nonprocedural programming that detects an event when it occurs and generates an appropriate response to that event (10)
Code whose sequence of execution is controlled or driven by events, rather than by a main program Most object-oriented code, including Hyperwire titles, is event-driven
A process such as a GUI that responds to events It enters a main loop, waiting for an event to occur After responding to the event, it returns to the loop and waits for the next event
Programming language characteristic that allows the development of programs to execute based on user-requested events rather than on a linear sequence through the program
A term for a programming methodology which is based on waiting for events, and processing each as it occurs
The property of an operating system or environment, such as Windows, that implies the existence of an idle loop When an event occurs, the idle loop is exited and event-handler code, specific to the event, is executed After the event handler has completed its operation, execution returns to the idle loop, awaiting the next event
A kind of program with a main loop that waits for events to occur Each event has an associated handler that is passed the details of the event as soon as it is detected This is in contrast to a polling program that frequently wakes up and checks for whether an event has happened yet, or a scheduled system that periodically wakes up and handles pending events