Repository navigation
e-stepper: the double arrows jump between breakpoints - #158
Conversation
Before a run the slider and the step buttons had nothing to act on: a lone disabled handle and label, and disabled buttons. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Blueprint labelled every s-th value from the first, so with 174 steps the right end read 163. The slider now runs from 0 (the start) to the number of steps, and always labels both ends. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The double arrows and the a / e keys go to the previous / next breakpoint() statement, or to the first / last step when there is none, as in the stepper. Needs the engine to mark them (py-slang#527). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Blueprint's Slider needs max > min; with one state it was 0..0. The slider is now 0..1 and disabled then. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
@codex review |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. Keep them coming! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
1 participant
As in the stepper (chapters 1 and 2 / Python): the double arrows and the
a/ekeys go to the previous / next breakpoint (a step whose marker hasredexNodeType: "DebuggerStatement"), or to the first / last step when there is none. The help text says so.The e-stepper engine marks
breakpoint()statements in source-academy/py-slang#527; until that is released, no step is marked and the arrows behave as before (first / last).Stacked on #157 (same controls); retargets to
mainonce that is merged.Tests: the next / previous breakpoint (and the fallbacks), and the buttons and keys on a run with two breakpoints.
🤖 Generated with Claude Code