How does event-driven programming work?

How does event-driven programming work?

• A. Programs run from start to finish without waiting for input.
• B. Programs execute only when there is an error.
• C. Programs require explicit user input before starting.
• D. Programs respond to events or user actions.

Answer: (D)

Event-driven programming is about designing software to react to events. A program sets up handlers for things that can happen—like a button being clicked, a key being pressed, or a timer firing—and then the environment waits for those events and calls the corresponding code when they occur. The program essentially sits idle until something happens, and the flow of execution is driven by user actions or other events rather than a fixed start-to-end sequence. A common example is a graphical user interface, where clicking a button runs code to perform a task, such as saving data or opening a dialog.

Event-driven programming is about designing software to react to events. A program sets up handlers for things that can happen—like a button being clicked, a key being pressed, or a timer firing—and then the environment waits for those events and calls the corresponding code when they occur. The program essentially sits idle until something happens, and the flow of execution is driven by user actions or other events rather than a fixed start-to-end sequence. A common example is a graphical user interface, where clicking a button runs code to perform a task, such as saving data or opening a dialog.