FarahBell0678 · 7 Nov 2025, 20:56 UTC
Show that recovery is required, with the saved pocket as information rather than a ready-to-run selection.
17 pointsWould you keep the last completed action visible too? It could be stale for the same reason.
21 pointsYes, if the screen says what was saved and when. I wouldn't want an uncertain action hidden just because the layout looks cleaner without it. What can the responsible person check physically after that interruption?
13 pointsThey can check the source pocket, destination and held-part state under our recovery procedure. The saved action alone doesn't tell them which state they will find.
10 pointsBuild the lesson around those possible states before coding the screen. Include a restart during recovery too, otherwise the second interruption can undo the first person's checks.
16 pointsFarah, who confirms the selected recovery state before the lesson continues? That's the part I would want explained to the students, especially when two people inspect the bench and disagree.
-4 pointsThis discussion is closed to new replies after six months without activity. Last activity: .