Adding Interactivity: Events

Active learning builds student understanding of events because programming requires students to see cause-and-effect in real time. Events transform static code into responsive tools, so hands-on trials help students move from abstract ideas to concrete actions they can control.

• Foundation
• Technologies
• 4 activities
• 20 min–35 min

Learning Objectives

1. Explain how an event block triggers a specific action in a block-based program.
2. Design a simple program that responds to a keyboard event, such as pressing the space bar.
3. Compare and contrast the functionality of different event blocks, like 'when flag clicked' and 'when this sprite clicked'.
4. Identify the user action that corresponds to a given event block in a program.

Experiential Learning

⏱ 25 min·Pairs

Pairs: Key Response Challenge

Pairs select a sprite and add 'when space key pressed' to make it jump, plus 'when right arrow pressed' to move right. They test by taking turns pressing keys, then debug if actions fail. Swap roles to refine the code.

Prepare & details

Explain how an 'event' makes a program respond to user actions.

Facilitation Tip: During the Key Response Challenge, circulate with a timer and verbally count down the rounds to keep pairs focused and energized.

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

⏱ 35 min·Small Groups

Small Groups: Event Story Builder

Groups create a simple story: 'when flag clicked' starts narration, 'when A key pressed' shows next scene with sound. They sequence three events and present to class. Adjust based on peer feedback.

Prepare & details

Design a program that starts when a specific key is pressed.

Facilitation Tip: For the Event Story Builder, hand out sticky notes in three colors to mark where each event type begins in their story code.

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

⏱ 20 min·Individual

Individual: Event Remix Hunt

Students open a sample project, identify all event blocks, and remix by adding 'when space key pressed' for a new action like color change. Share one change with a partner.

Prepare & details

Compare different events that can trigger actions in a program.

Facilitation Tip: In the Event Remix Hunt, provide printed starter projects on paper so students can annotate directly with notes about event triggers and outcomes.

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 Demo Relay

Project one screen; class suggests events like 'when flag clicked' for start, keys for controls. Teacher codes live, students predict outcomes and verify by testing together.

Prepare & details

Explain how an 'event' makes a program respond to user actions.

Facilitation Tip: Run the Event Demo Relay with clear roles: one student codes, one narrates the event flow, and one records observations about what happened.

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

Teach events by modeling how to isolate the trigger from the action. Use think-alouds to show how to read 'when space key pressed' and trace the code that follows. Avoid rushing to combine multiple events before students grasp the basics. Research shows that students learn event-driven logic best when they test one event at a time and observe immediate feedback.

What to Expect

Successful learning shows when students can explain why events are needed, design programs that start with user triggers, and compare different event types in their projects. Students should articulate how events connect user actions to program responses clearly and confidently.

Watch Out for These Misconceptions

Common Misconception

During the Key Response Challenge, watch for students who believe their program should start automatically without any event block.

What to Teach Instead

Pause the class and show two side-by-side projects: one with 'when flag clicked' and one without. Ask students to run both and explain why the first project waits for user input before running.

Common Misconception

During the Event Story Builder, watch for students who assume they can only use one event in their entire program.

What to Teach Instead

Point to the sticky notes and ask students to stack multiple event blocks. Have them run the project and describe how each event runs independently when triggered.

Common Misconception

During the Event Remix Hunt, watch for students who think events only work at the start of the program.

What to Teach Instead

Demonstrate a sprite that loops a movement and then respond to a key press in the middle of that loop. Ask students to remix their projects to test mid-program events and share findings in a quick discussion.

Assessment Ideas

Exit Ticket

After the Key Response Challenge, provide a snippet with a 'when flag clicked' block and a sprite action. Ask students to write one sentence explaining what will happen when the flag is clicked and one sentence naming the event type.

Quick Check

During the Event Story Builder, ask: 'What event makes your sprite start moving?' Listen for responses like 'when the green flag is clicked' or 'when the space key is pressed' and provide immediate feedback.

Discussion Prompt

After the Event Remix Hunt, pose the question: 'Imagine your sprite needs to jump when clicked and spin when the up arrow is pressed. What events would you use?' Encourage students to share ideas and justify their choices in pairs before whole-class sharing.

Extensions & Scaffolding

• Challenge: Ask students to design a project where two different events control the same sprite, such as making it move and change color with separate keys.
• Scaffolding: Provide a partially completed project with one event block already placed and ask students to add one more event of their choice.
• Deeper: Introduce broadcast messages as events and have students create a chain reaction where one sprite’s action triggers another sprite’s movement.

Key Vocabulary

Event	An action that a program can detect, like clicking a mouse or pressing a key. Events make programs interactive by starting actions.
Event Block	A special block in coding that waits for a specific event to happen before running the code stacked below it.
Trigger	The specific event that causes a block of code to run. For example, pressing the 'space' key can trigger a sprite to move.
User Action	Something a person does to interact with a program, such as clicking a button or typing on a keyboard.