Computing · Year 3

Active learning ideas

Using Multiple Events and Conditions

Active learning works because students need to see how events and conditions interact in real time. When they test two inputs at once on a shared screen, their misconceptions about sequence and logic become visible immediately. This hands-on testing helps them move from abstract ideas to concrete understanding.

• National Curriculum Attainment Targets
• KS2: Computing - Programming
• KS2: Computing - Algorithms

• 25–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Plan-Do-Review
• 35 min · Pairs

Pair Coding Challenge: Multi-Control Character

Pairs use block-based software to code a sprite that jumps on spacebar, moves left-right on arrows, and changes colour if touching an edge. First, brainstorm controls together. Then code, test, and swap roles to add one condition each. Share working games with the class.

Analyze how multiple events can make a character jump and run simultaneously.

Facilitation Tip

During Pair Coding Challenge, assign roles so one student types while the other tests, ensuring both engage with the logic.

What to look for

Provide students with a short code snippet that uses two event listeners and one conditional. Ask them to write down what will happen when the user presses a specific key, and what will happen if they click the mouse.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 02

• Plan-Do-Review
• 45 min · Small Groups

Small Group Debug Relay: Condition Fixes

Divide code with multiple events into stations, each with a bugged condition, like endless jumping. Groups rotate, fix one issue per station using test runs, and note changes. Regroup to combine fixes into a full game.

Design a program that uses different events to control different aspects of a game.

Facilitation Tip

In Small Group Debug Relay, have each group start with the same buggy code to highlight common misconceptions about condition placement.

What to look for

Observe students as they work on their game designs. Ask targeted questions like: 'What event is this code listening for?' or 'What needs to be true for the character to jump?' Note which students can articulate the relationship between events and conditions.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 03

• Plan-Do-Review
• 50 min · Whole Class

Whole Class Game Design Share: Event Mapping

Students sketch game ideas with multiple events on paper first. Code individually, then present to class for votes on best conditions. Class votes and suggests improvements before final tweaks.

Evaluate the importance of clear conditions in event-driven programming.

Facilitation Tip

For Whole Class Game Design Share, display student code on the board so the class can see how different event-condition pairs achieve the same goal.

What to look for

Pose a scenario: 'Imagine a character in a game needs to pick up a coin, but only if it's standing on the ground. How would you use events and conditions to make this happen?' Facilitate a brief class discussion on their proposed solutions.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

Activity 04

• Plan-Do-Review
• 25 min · Individual

Individual Extension: Custom Condition Game

Each student adds two personal conditions to a base game template, such as scoring only if moving fast. Test against self-set goals and record video explanations of event interactions.

Analyze how multiple events can make a character jump and run simultaneously.

Facilitation Tip

During Individual Extension, provide a starter project with placeholder sprites to reduce cognitive load and focus on logic.

What to look for

Provide students with a short code snippet that uses two event listeners and one conditional. Ask them to write down what will happen when the user presses a specific key, and what will happen if they click the mouse.

• Remember
• Apply
• Analyze
• Self-Management
• Decision-Making
• Self-Awareness

A few notes on teaching this unit

Teach this topic by modeling parallel event handling first, using a shared screen to show how multiple inputs can trigger actions at the same time. Avoid teaching conditions in isolation; instead, connect them directly to events so students see their purpose. Research shows that students grasp logic better when they test and debug their own code rather than watching a teacher demonstrate.

Successful learning looks like students designing a character that moves with multiple inputs and uses conditions to control actions. They should explain why certain conditions are necessary and adjust their code based on peer feedback. By the end, they can articulate how events and conditions work together to create interactive rules.

---

Watch Out for These Misconceptions

• During Pair Coding Challenge, watch for students who assume events must happen one at a time and write code that forces sequential inputs.

  After the pair shares their movement rules, ask the class to press two keys at once. Have students observe that both actions occur simultaneously, then revise their code to allow parallel inputs.

• During Small Group Debug Relay, students may think conditions are optional or decorative.

  During the relay, pause the group after they fix the first bug and ask them to disable their condition blocks. Have them test the program and describe what happens without the logic gates controlling the actions.

• During Whole Class Game Design Share, students might believe adding more events always improves the game.

  After reviewing a shared design, ask the class to identify which events feel unnecessary or confusing. Guide a discussion about how each event serves a clear purpose and how conditions help manage complexity.

---

Methods used in this brief

• Plan-Do-Review