Fix #106208: data-block socket defaults not used for node group #107179
No reviewers
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
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
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
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
EEVEE & Viewport
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
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
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
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#107179
Loading…
Reference in New Issue
No description provided.
Delete Branch "JacquesLucke/blender:node-group-default-id"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This is an alternative fix to #106816.
The main challenge is to avoid dangling pointers. Currently, the lifetime of socket declarations is somewhat unbounded (at least we didn't restrict it explicitly yet). Therefore, storing non-owning pointers in it tricky. For ID pointers one could potentially use the foreach-id iterator to update pointers in declarations as well, but that's a bit out of scope and might not be the right solution anyway, since it's not obvious that all node declarations are reachable from IDs stored in
bmain
.The solution now is to use a callback that retrieves the right ID pointer when it is used. The important thing is that the callback does not capture any potentially dangling pointer either.
@ -438,0 +440,4 @@
ID *id = this->default_value_fn(node);
/* Assumes that all ID sockets like #bNodeSocketValueObject and #bNodeSocketValueImage have the
* ID pointer at the start of the struct. */
*(ID **)socket.default_value = id;
C-style cast here
It's not pretty but I think it makes sense, thanks.
I guess the alternative is including these default ID pointers in
node_foreach_id
so they will be remapped? I don't have a preference either way really, just checking my understanding.@ -158,6 +158,8 @@ class StringBuilder : public SocketDeclarationBuilder<String> {
class IDSocketDeclaration : public SocketDeclaration {
public:
const char *idname;
/** Get the default ID pointer for this socket. This is a function to avoid dangling pointers. */
Maybe add
, since
bNode::idpointers are remapped as
IDpointers change, but pointers in socket declarations are not managed the same way.
@ -128,0 +140,4 @@
const bNodeTree &ntree = *reinterpret_cast<const bNodeTree *>(node.id);
const bNodeSocket *io_socket;
if (in_out == SOCK_IN) {
if (socket_index < ntree.interface_inputs().size()) {
Hmm, why would the socket index be out of bounds here? Does this function object live past some changes to the group interface? If so, maybe worth noting that in a comment.
The problem is, I don't think we know for sure how long this will live currently. At least I don't know.
I mentioned that in the PR description.
@ -128,0 +140,4 @@
const bNodeTree &ntree = *reinterpret_cast<const bNodeTree *>(node.id);
const bNodeSocket *io_socket;
if (in_out == SOCK_IN) {
/* Better be save than sorry when the underlying node group changed. */
save
->safe