Skip to content

Implement loop node handling in VisualStudioBlueprintDebuggerHelper#61

Open
laycnc wants to merge 1 commit intomicrosoft:mainfrom
laycnc:feature/blueprint-loop-node-path-simplify
Open

Implement loop node handling in VisualStudioBlueprintDebuggerHelper#61
laycnc wants to merge 1 commit intomicrosoft:mainfrom
laycnc:feature/blueprint-loop-node-path-simplify

Conversation

@laycnc
Copy link

@laycnc laycnc commented Jul 20, 2025

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.

image

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.

スクリーンショット 2025-07-20 031808 image

Specializations have been implemented for Loop nodes described in "StandardMacros".

ForLoop, ForLoopWithBreak, ForEachLoop, ForEachLoopWithBreak, ReverseForEachLoop, WhileLoop

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.

@laycnc
Copy link
Author

laycnc commented Jul 25, 2025

@microsoft-github-policy-service agree

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant