Events and User Interaction

Active learning works for events and user interaction because students must see, test, and revise how code responds to real-time input. Hands-on programming turns abstract triggers into visible outcomes, helping Year 7 students grasp that events wait for user actions before executing. This approach builds confidence as students immediately see cause and effect in their own projects.

• Year 7
• Computing
• 4 activities
• 25 min–45 min

Learning Objectives

1. Analyze how specific event blocks in Scratch initiate distinct sprite or stage actions.
2. Design an interactive game in Scratch that utilizes at least two different user input events.
3. Compare the functionality of 'when key pressed' and 'when sprite clicked' events to determine appropriate use cases.
4. Create a sequence of actions triggered by a single event block in Scratch.
5. Explain the cause-and-effect relationship between a user action and a program response in a Scratch project.

Experiential Learning

⏱ 35 min·Pairs

Pair Programming: Key Press Dodge Game

Pairs create a sprite that moves left or right when arrow keys are pressed to dodge falling objects. One partner codes the event blocks while the other tests and suggests changes; swap roles after 10 minutes. End with a class share-out of best features.

Prepare & details

Analyze how different events can initiate actions in a Scratch program.

Facilitation Tip: During Pair Programming, circulate and ask each pair to explain which event block controls their sprite’s movement before they test it, reinforcing the connection between code and outcome.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 45 min·Small Groups

Small Groups: Click-to-Score Quiz

Groups build a quiz where clicking correct sprite answers advances to the next question and adds points. Use 'when sprite clicked' events chained with broadcasts. Groups demo their quizzes and vote on the most engaging one.

Prepare & details

Design an interactive game in Scratch that responds to user input.

Facilitation Tip: In Small Groups, ask students to swap projects halfway through and predict how the Click-to-Score Quiz will react to clicks before testing it themselves.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 30 min·Whole Class

Whole Class: Event Remix Challenge

Project a shared Scratch file with basic events. Students suggest and vote on additions like 'when space key pressed' for jumps, then implement as a class. Discuss how events make the program more interactive.

Prepare & details

Compare the use of 'when key pressed' versus 'when sprite clicked' events.

Facilitation Tip: For the Whole Class Event Remix Challenge, provide a starter project with broken or missing events so students focus on debugging rather than starting from scratch.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Experiential Learning

⏱ 25 min·Individual

Individual: Personal Event Diary

Students remix a template to log daily events by clicking sprites or pressing keys to change backgrounds and add notes. Export and reflect on how events captured their choices effectively.

Prepare & details

Analyze how different events can initiate actions in a Scratch program.

Facilitation Tip: For the Individual Personal Event Diary, model annotating one event block with a sticky note that explains its purpose before students begin.

Setup: Varies; may include outdoor space, lab, or community setting

Materials: Experience setup materials, Reflection journal with prompts, Observation worksheet, Connection-to-content framework

• Apply
• Analyze
• Evaluate
• Self-Awareness
• Self-Management
• Social Awareness

Teaching This Topic

Start by demonstrating how events wait for triggers using a simple starter project. Avoid overwhelming students with too many event types at once. Focus on one or two per activity, then gradually introduce more through comparison and discussion. Research shows students learn best when they observe immediate feedback, so prioritize quick testing cycles over long explanations. Use collaborative debugging to normalize mistakes as part of learning, not failures.

What to Expect

Successful learning looks like students confidently linking events to actions, choosing appropriate triggers for user control, and explaining why one event type works better than another. They should debug simple issues independently and collaborate to remix projects with layered interactions. By the end, students can design a small interactive program from scratch using at least two different event types.

Watch Out for These Misconceptions

Common Misconception

During Pair Programming, watch for students who assume the Key Press Dodge Game runs automatically without their input.

What to Teach Instead

Remind pairs to test the project before coding, pointing out that the character only moves when they press a key. Ask them to observe the script area to see which blocks light up when the key is pressed.

Common Misconception

During Small Groups, watch for students who believe all events work the same way regardless of type.

What to Teach Instead

Have groups compare the Click-to-Score Quiz’s 'when sprite clicked' event with a 'when green flag clicked' event from their starter project. Ask them to describe what happens when each is triggered and why the results differ.

Common Misconception

During Whole Class Event Remix Challenge, watch for students who think only one event can control a sprite at a time.

What to Teach Instead

Direct students to layer events in their remix, such as adding a 'when key pressed' event to change direction and a 'when sprite clicked' event to change color. Ask them to test both events on the same sprite to observe simultaneous control.

Assessment Ideas

Exit Ticket

After Pair Programming, provide each student with a screenshot of a Scratch project using 'when key pressed' and 'when sprite clicked'. Ask them to label which event block moves the sprite and which makes it say 'Ouch!'.

Quick Check

During Small Groups, circulate and ask each group: 'What event block makes the sprite disappear when clicked? What would happen if we changed it to 'when green flag clicked'?' Listen for their reasoning about user-triggered versus automatic execution.

Discussion Prompt

After the Whole Class Event Remix Challenge, pose the question: 'How did remixing change the way you think about events? Give one example from your project where layering events improved the user experience.' Facilitate a brief discussion to reinforce the concept of responsive programming.

Extensions & Scaffolding

• Challenge early finishers to add a second event type that changes the sprite’s costume when a different key is pressed.
• Scaffolding for struggling students: Provide a partially completed version of the Key Press Dodge Game with event blocks already placed but missing code.
• Deeper exploration: Ask students to research and add a broadcast event to coordinate actions between two sprites in their Click-to-Score Quiz project.

Key Vocabulary

event	A signal that tells a program something has happened, like a mouse click or a key press, which can then trigger a specific action.
event handler	A block of code in Scratch that waits for a specific event to occur and then runs the commands associated with that event.
user input	Information or commands provided by a person interacting with a program, such as pressing a key or clicking a button.
sprite	A character or object in a Scratch project that can be moved, programmed, and interacted with.