Skip to content

fix: register gizmos and package import path at Nuke startup#1

Open
semx2a wants to merge 1 commit into
Code2Collapse:mainfrom
semx2a:studio/01-plugin-loading
Open

fix: register gizmos and package import path at Nuke startup#1
semx2a wants to merge 1 commit into
Code2Collapse:mainfrom
semx2a:studio/01-plugin-loading

Conversation

@semx2a

@semx2a semx2a commented Jul 2, 2026

Copy link
Copy Markdown

Part 1 of a 5-PR series (each later PR builds on the previous one — merging them in order without squash will automatically shrink the next PR's diff to its own commit).

The package ships no Nuke-level init.py, so ./gizmos is never added to the plugin path — creating the node fails with H2_SamViT: Unknown command — and the H2_SamViT_Gizmo package isn't importable from the gizmo's knob callbacks. This adds an init.py that registers ./gizmos and puts the package's parent directory on the plugin path (which Nuke also adds to sys.path).

The package had no Nuke-level init.py, so ./gizmos was never added to the
plugin path (H2_SamViT: "Unknown command") and the H2_SamViT_Gizmo package
itself was not importable from gizmo knob callbacks. Add an init.py that
registers ./gizmos and puts the package's parent on the plugin path (which
Nuke also adds to sys.path).

Also ignore .codegraph/ tool artifacts.
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