Implement loop node handling in VisualStudioBlueprintDebuggerHelper#61
Open
laycnc wants to merge 1 commit intomicrosoft:mainfrom
Open
Implement loop node handling in VisualStudioBlueprintDebuggerHelper#61laycnc wants to merge 1 commit intomicrosoft:mainfrom
laycnc wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
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.
VisualStudioBlueprintDebuggerHelper is a plugin that can hold the execution path of a Blueprint and display it in a debugger.
When using Loop-type nodes, the paths displayed are huge and difficult to use for debugging.
The routes are stored for the number of loops * the number of nodes after the LoopBody.
When you run the above Blueprint, stop the debugger at PrintString and look at the Blueprint debugger, you will see the following.
Debugging is difficult because a huge number of Node information is displayed.
Specializations have been implemented for Loop nodes described in "StandardMacros".
Simplification is done by deleting the last Node passed each time the LoopBody of a Loop-type node is passed.
This allows for minimal display.