Code.org App Lab help: fixing events, variables and screens

// ours: a score that never climbs past 1
onEvent("addButton", "click", function() {
  var score = 0;            // a new local score, every click
  score = score + 1;
  setText("scoreLabel", score);
});

// our check, with stand-in functions in Node:
// click 1: scoreLabel shows 1
// click 2: scoreLabel shows 1
// click 3: scoreLabel shows 1

Ours. We checked the logic in Node 22 with stand-in versions of onEvent and setText that behave as the documentation describes; this was not a run inside App Lab. Each click creates a brand-new local score set to 0, adds 1, and throws it away.

// ours: the counter pattern, variable created once
var score = 0;              // global: created once, at the top

onEvent("addButton", "click", function() {
  score = score + 1;        // no var here
  setText("scoreLabel", score);
});

// click 1: 1   click 2: 2   click 3: 3

Ours, same check. This is the shape the documentation calls the counter pattern with an event: the variable gets its first value once, and each event updates it.

// ours: the user types 10 into priceInput
var a = getText("priceInput") + 5;     // "10" + 5
console.log(a);                        // 105

var b = getNumber("priceInput") + 5;   // 10 + 5
console.log(b);                        // 15

Ours, same check in Node. The getNumber documentation warns that getText can read a text input too, but a number will be converted to a string and arithmetic will not be possible with the result. The console.log page gives the same lesson: "5" + "3" displays 53.