Custom Node Trees: Selected node tree is lost when editor is switched to other node editors #100306

New Issue

Eyad Ahmed · 2022-08-10T00:24:51+02:00

Eyad Ahmed commented

2022-08-10 00:24:51 +02:00

Run the official Custom Nodes Python template
Switch to the newly registered Custom Node Tree editor
Create a node tree
Switch to another node editor (Shader Editor for example)
Switch back to the custom node tree editor
The selected node tree was switched back to None

1. Run the official Custom Nodes Python template 2. Switch to the newly registered Custom Node Tree editor 3. Create a node tree 4. Switch to another node editor (Shader Editor for example) 5. Switch back to the custom node tree editor 6. The selected node tree was switched back to None

Eyad Ahmed commented

2022-08-10 00:24:51 +02:00

Added subscriber: @IyadAhmed

Iliya Katushenock commented

2022-08-10 01:39:11 +02:00

Added subscriber: @mod_moder

Iliya Katushenock commented

2022-08-10 01:39:11 +02:00

I confirm. I suspect that this is due to the fact that the blender does not know what context to store information about the selected node tree behind? As if you deleted the selected object with material and it was not selected in the editor

Found some code that I think does a lookup on a node editor change. I'm not sure I'm well versed in the python api yet, but it looks like this doesn't take python into account node_context_path.cc

I confirm. I suspect that this is due to the fact that the blender does not know what context to store information about the selected node tree behind? As if you deleted the selected object with material and it was not selected in the editor Found some code that I think does a lookup on a node editor change. I'm not sure I'm well versed in the python api yet, but it looks like this doesn't take python into account [node_context_path.cc ](https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/space_node/node_context_path.cc)

Pratik Borhade commented

2022-08-10 02:52:16 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Pratik Borhade commented

2022-08-10 02:52:20 +02:00

Added subscriber: @PratikPB2123

Eyad Ahmed commented

2022-08-10 11:09:24 +02:00

In #100306#1401979, @mod_moder wrote:
I confirm. I suspect that this is due to the fact that the blender does not know what context to store information about the selected node tree behind? As if you deleted the selected object with material and it was not selected in the editor

Found some code that I think does a lookup on a node editor change. I'm not sure I'm well versed in the python api yet, but it looks like this doesn't take python into account node_context_path.cc

Awesome, this is definitely a very helpful clue

> In #100306#1401979, @mod_moder wrote: > I confirm. I suspect that this is due to the fact that the blender does not know what context to store information about the selected node tree behind? As if you deleted the selected object with material and it was not selected in the editor > > > Found some code that I think does a lookup on a node editor change. I'm not sure I'm well versed in the python api yet, but it looks like this doesn't take python into account [node_context_path.cc ](https://developer.blender.org/diffusion/B/browse/master/source/blender/editors/space_node/node_context_path.cc) Awesome, this is definitely a very helpful clue

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Custom Node Trees: Selected node tree is lost when editor is switched to other node editors #100306