An Empty Panel is Shown in The Modifier while not in Group Node. #129087

Closed
opened 2024-10-16 04:23:01 +02:00 by Gerstmann Bradley · 3 comments

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.94

Blender Version
Broken: version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-13 22:49, hash: 72be365c6ba6
Broken: 4.2

Short description of error
image
image

Not sure If it is a known limitation in Modifier Panel.

A side note is that I noticed that while sockets can be chosen to "hide in modifier", panels can't be chosen to do so.
I want to always mention the importance for a node group to be used as both group node and modifier, to reduce the amount of nodes over all. Otherwise there can be many nodes with the same function only because they are respectively designed for group node and modifier.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 4070 SUPER/PCIe/SSE2 NVIDIA Corporation 4.6.0 NVIDIA 560.94 **Blender Version** Broken: version: 4.3.0 Beta, branch: blender-v4.3-release, commit date: 2024-10-13 22:49, hash: `72be365c6ba6` Broken: 4.2 **Short description of error** ![image](/attachments/7485568b-82cb-435d-8136-6fdbf66ddd65) ![image](/attachments/92a06b75-7b0d-4c32-9c60-620385f141bc) Not sure If it is a known limitation in Modifier Panel. A side note is that I noticed that while sockets can be chosen to "hide in modifier", panels can't be chosen to do so. I want to always mention the importance for a node group to be used as both group node and modifier, to reduce the amount of nodes over all. Otherwise there can be many nodes with the same function only because they are respectively designed for group node and modifier.
Gerstmann Bradley added the
Status
Needs Triage
Severity
Normal
Type
Bug
labels 2024-10-16 04:23:01 +02:00
Member

Hi, thanks for the report. If you ask me, panel tree-view element in modifier panel should be visible if it has any child element (similar to gpv3 groups in dopesheet).

Hi, thanks for the report. If you ask me, panel tree-view element in modifier panel should be visible if it has any child element (similar to gpv3 groups in dopesheet).
Member

Like this:

diff --git a/source/blender/modifiers/intern/MOD_nodes.cc b/source/blender/modifiers/intern/MOD_nodes.cc
index 67a04bda3a1..80b63de007b 100644
--- a/source/blender/modifiers/intern/MOD_nodes.cc
+++ b/source/blender/modifiers/intern/MOD_nodes.cc
@@ -2256,6 +2256,9 @@ static void draw_interface_panel_content(const bContext *C,
   for (const bNodeTreeInterfaceItem *item : interface_panel.items()) {
     if (item->item_type == NODE_INTERFACE_PANEL) {
       const auto &sub_interface_panel = *reinterpret_cast<const bNodeTreeInterfacePanel *>(item);
+      if (sub_interface_panel.items_num == 0) {
+        continue;
+      }
       NodesModifierPanel *panel = find_panel_by_id(nmd, sub_interface_panel.identifier);
       PointerRNA panel_ptr = RNA_pointer_create(
           modifier_ptr->owner_id, &RNA_NodesModifierPanel, panel);
Like this: ```Diff diff --git a/source/blender/modifiers/intern/MOD_nodes.cc b/source/blender/modifiers/intern/MOD_nodes.cc index 67a04bda3a1..80b63de007b 100644 --- a/source/blender/modifiers/intern/MOD_nodes.cc +++ b/source/blender/modifiers/intern/MOD_nodes.cc @@ -2256,6 +2256,9 @@ static void draw_interface_panel_content(const bContext *C, for (const bNodeTreeInterfaceItem *item : interface_panel.items()) { if (item->item_type == NODE_INTERFACE_PANEL) { const auto &sub_interface_panel = *reinterpret_cast<const bNodeTreeInterfacePanel *>(item); + if (sub_interface_panel.items_num == 0) { + continue; + } NodesModifierPanel *panel = find_panel_by_id(nmd, sub_interface_panel.identifier); PointerRNA panel_ptr = RNA_pointer_create( modifier_ptr->owner_id, &RNA_NodesModifierPanel, panel); ```

I remember there was some refactoring to properly support optional panel visibility, but not sure\

I remember there was some refactoring to properly support optional panel visibility, but not sure\
Blender Bot added
Status
Resolved
and removed
Status
Needs Info from Developers
labels 2024-10-21 15:48:25 +02:00
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Code Documentation
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Viewport & EEVEE
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Asset Browser Project
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Module
Viewport & EEVEE
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Severity
High
Severity
Low
Severity
Normal
Severity
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#129087
No description provided.