Repository navigation
Live Log while stepping: follows every run, run selector, highlights the latest step - #194
Merged
Merged
Conversation
…tep highlighted The feed counted the lines already shown and appended only the tail of the session's current log. Each run has its own, shorter log, so after Jump (or stepping off the end of a run) nothing reached the tree and run 1's rows stayed on screen. The Live Log is now a panel with a run selector (Run N of M, previous/next), shows the run being stepped and follows it into the next run, keeps finished runs readable while stepping on, tints and bolds the rows the latest step added, keeps the newest row in view, and holds at most the newest 5,000 rows of a run (saying so). The Results dock's live view now lists every run so far, not just the current one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #193.
The Live Log kept a count of lines already shown and appended only
session.logs[count:]. Each run has its own shorter log, so after Jump or after stepping off the end of a run nothing reached the tree, and run 1's rows stayed on screen.The Live Log is now
LiveLogPanel(raptor/gui/ui/live_log_panel.py):Docs: manual (stepping section) and the debugger chapter;
manual.htmlandbook.htmlregenerated.Tests:
tests/unit/test_gui_live_log_runs.py(8): follows every step, run 2 shows its own rows after a Jump, going back to run 1 and forward again, highlight moves with each step, newest row scrolled into view, row cap, Results dock lists runs, panel cleared with the session. Step jump, Results, dock layout, run controls and docs gates pass; ruff and the mypy gate are clean.