WIP: Add Expression Variable Monitoring/Debug API#971
Draft
WIP: Add Expression Variable Monitoring/Debug API#971
Conversation
kblaschke
changed the title
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
1 participant
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.
Adds a new API for debugging/monitoring expression variables within the active preset.
Users of the library can register arbitrary variables to be monitored in the different code blocks, which helps to identify issues with both presets and the expression parser. It's also helpful for preset authors, as they can track (and potentially graph) variable values in real time, and aren't limited to the single
monitorvariable Milkdrop provides.For code blocks which are executed more than once, e.g. frame per-point, custom shape per-frame and custom wave per-point expressions, the API will return an array of all values, one for each executed instance.
Closes #664