Build a crappy debugger #486
Merged
Conversation
This file contains 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.
This PR adds a simple debugger that can be enabled with
--debugor-din the renderer binary.I noticed an issue with the rendering of borders and vello, it seems like they are clipping into the "main" rect, that has the border.
(Note for the image below, i don't had the gosub logo in my work folder, so it is missing, but it still can be inspected by the debugger)
We could add some lines for alignment and information about what you are actually inspecting, but thats something for later.
It's really nice to see finally "interactivity" and not only static pages rendering with gosub! 😀