Technologies · Foundation

Active learning ideas

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.

• ACARA Content Descriptions
• AC9TDEFP01

• 20–35 min
• Pairs → Whole Class
• 4 activities

Activity 01

• 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.

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.

What to look for

Provide students with a simple program snippet showing an event block (e.g., 'when flag clicked') and a sprite action. Ask them to write one sentence explaining what will happen when the flag is clicked and one sentence describing what kind of user action triggers this event.

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

Activity 02

• 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.

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.

What to look for

During a coding activity, ask students: 'What event makes your sprite start moving?' or 'If you want your sprite to say 'Hello' when you click it, what event block would you use?' Observe student responses and provide immediate feedback.

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

Activity 03

• 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.

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.

What to look for

Pose the question: 'Imagine you are making a program where a cat chases a mouse. What different events could make the cat start moving?' Encourage students to share ideas like clicking the cat, pressing a key, or when the mouse appears.

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

Activity 04

• 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.

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.

What to look for

Provide students with a simple program snippet showing an event block (e.g., 'when flag clicked') and a sprite action. Ask them to write one sentence explaining what will happen when the flag is clicked and one sentence describing what kind of user action triggers this event.

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

A few notes on teaching this unit

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.

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

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

  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.

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

  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.

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

  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.

---

Methods used in this brief

• Experiential Learning