Skip to content

fix: guard against None compositor node group (#18)#19

Open
SAY-5 wants to merge 1 commit into
gregzaal:masterfrom
SAY-5:fix/issue-18-compositor-none
Open

fix: guard against None compositor node group (#18)#19
SAY-5 wants to merge 1 commit into
gregzaal:masterfrom
SAY-5:fix/issue-18-compositor-none

Conversation

@SAY-5

@SAY-5 SAY-5 commented May 11, 2026

Copy link
Copy Markdown

Resolves #18.

get_compositor_node_group() returns None when a scene has no compositing node tree (e.g. when scene.compositing_node_group exists but is unset, or scene.node_tree is None). The compositing scenes panel called .name on the result unconditionally, raising AttributeError: 'NoneType' object has no attribute 'name' whenever the panel was drawn while the active scene lacked a compositing tree.

The reporter (Cristóbal Vila) hit this on Blender 5.1.1 / macOS when pressing Alt-R in the Shader Editor with the Matalogue Tree Panel open, and also when simply selecting different objects. The traceback points to the line in MATALOGUE_PT_compositing_scenes.draw that accesses .name on the result.

Stores the result in comp_group once and guards both .name and the later .nodes access in the same function.

get_compositor_node_group() returns None when a scene has no
compositing node tree. The compositing scenes panel called .name on
the result unconditionally, raising AttributeError whenever the panel
was drawn while the active scene lacked a compositing tree.

Resolves issue gregzaal#18.

Signed-off-by: SAY-5 <say.apm35@gmail.com>
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.

Errors using Matalogue 1.5.1 with Blender 5.1.1 on a Mac

1 participant