fix bypass hotkey in vue nodes and fix node data instrumentation setup issue when switching to Vue nodes after initial load #5715
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.
Summary
Fixed Vue node keybinding target element ID to enable bypass/pin/collapse hotkeys in both LiteGraph and Vue rendering modes.
Also fixed a bug when starting in litegraph mode => switching to Vue nodes without reloading =>
graph.onTriggeris set toundefinedwhich interferes with proper setup of node data instrumentation, among other things.Changes
targetElementIdfromgraph-canvastograph-canvas-containerfor node manipulation commands (parent of both the canvas and transform pane -- vue nodes container).onTriggerhandler restoration in slot layout sync to prevent Vue node manager conflictsReview Focus
Event handler precedence between Vue nodes and LiteGraph systems during mode switching, ensuring hotkeys work consistently across rendering modes.
┆Issue is synchronized with this Notion page by Unito