Fix #106208: Initialize socket value by declaration callback if value is data block #106816

Closed
Iliya Katushenock wants to merge 4 commits from mod_moder:default_value_cb into main

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

We cannot store pointer to data blocks by value, because
in this case, declarations would have to be available
for visiting by the blender id visitor in order to be
able to delete or relink these pointers. For this reason,
in order to be scalable in the future, this is a callback.
The implementation can find up-to-date value at any time.

This approach also makes it possible not to make unnecessary
updates to the declaration in order to update the actual standard value.

We cannot store pointer to data blocks by value, because in this case, declarations would have to be available for visiting by the blender id visitor in order to be able to delete or relink these pointers. For this reason, in order to be scalable in the future, this is a callback. The implementation can find up-to-date value at any time. This approach also makes it possible not to make unnecessary updates to the declaration in order to update the actual standard value.
Iliya Katushenock added 4 commits 2023-04-11 16:32:38 +02:00
Iliya Katushenock changed title from Fix #106208: Initialize socket value by declaration callback if data is data block to Fix #106208: Initialize socket value by declaration callback if value is data block 2023-04-11 16:32:46 +02:00
Iliya Katushenock added this to the Nodes & Physics project 2023-04-11 16:32:53 +02:00
Iliya Katushenock added the
Interest
Geometry Nodes
label 2023-04-11 16:33:00 +02:00
Lukas Tönne reviewed 2023-04-12 08:58:27 +02:00
@ -128,0 +130,4 @@
bNodeTree &node_group, StringRefNull socket_name_p)
{
std::string socket_name = socket_name_p;
return [node_group = &node_group,
Member

I agree that we need to avoid ID pointers in the declarations. But this solves one problem by creating another: Now we have the bNodeTree bound in the callback.

A weak pointer of some kind seems to be needed here, so that ID management code does not have to worry about references stored in node declarations.

I agree that we need to avoid ID pointers in the declarations. But this solves one problem by creating another: Now we have the `bNodeTree` bound in the callback. A weak pointer of some kind seems to be needed here, so that ID management code does not have to worry about references stored in node declarations.
Author
Member

Trees cause refresh on their own. That is, it must be safe.
It would be possible to add a requirement to the topology cache in order to find a node from the socket and take its pointer to the tree. But this can increase the overhead. Or we can pass a node. But at one point it may require also a tree as well ... there is not enough some context

Trees cause refresh on their own. That is, it must be safe. It would be possible to add a requirement to the topology cache in order to find a node from the socket and take its pointer to the tree. But this can increase the overhead. Or we can pass a node. But at one point it may require also a tree as well ... there is not enough some context
Author
Member
https://projects.blender.org/blender/blender/pulls/107179
Iliya Katushenock deleted branch default_value_cb 2023-04-20 16:56:31 +02:00

Pull request closed

Sign in to join this conversation.
No reviewers
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 Assignees
2 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#106816
No description provided.