Match an Event to Its Handler

Supplied materials

• Paper and pencil; answers may also be spoken or typed.
• All cases, labels, numbers and rules are supplied on this page. No real account, private information or purchase is needed.

Learn the idea

An event is something a program notices, such as a click or key press. An event handler describes the response. A program should distinguish events so one control does not unexpectedly perform another control’s job. The supplied handler table is a paper model; it runs no real code.

Look up the exact event in the handler table and apply only its stated response. The response to one button does not automatically run for every event.

Use this supplied case: Event Start. Handlers: Start opens story; Back opens menu; Read plays voice; Help shows steps. What response runs? Use the details in this example. Say which detail helped you choose. This pretend example does not tell us how every real system works.

1. Follow the worked example one step at a time. Say or draw what happens.
2. Look up the exact event in the handler table and apply only its stated response.
3. Say which detail makes the example answer fit. Pick another answer and say why it does not fit.
4. Try the question and practice questions. Read the rule again if your answer does not match the explanation.

Check your reasoning

Your answer is temporary and is not saved to an account. Download your current answer before leaving or reloading. Written work on paper or in another app stays in your own file.

Take it further

New handlers: Open→page, Close→menu. Expected: Close invokes the menu response and does not implicitly run the Open response.

Nothing here is saved to an account or sent to a teacher. The answer download includes your current choice and any checked feedback. It does not include choices from the separate More practice section. Download that section separately.