[Renderer process error] Dynamic tab name

Community Usage questions
1

Hello.

I try to link a variable for a dynamic tab name thanks to a input widget on it.
I add a variable on the tab variables link to the value of an input on the tab (it's working fine)

#{extend(@{parent.variables},
{
"p": 1,
"name": @{preset_0_1_name}
}
)}

Then, I create a new tab with a clone of the panel of the tab with new variables link to the clone of the input widget (I have 40 tabs for preset). On the editor I can modify with this system the tab name. But when I reload the session I have this error :

[Renderer process error]
Uncaught NotFoundError: Failed to execute 'replaceChild' on 'Node': The node to be replaced is not a child of this node.
at updateWidget (src/client/app/editor/data-workers.js:106:35)
at reCreateWidget (src/client/app/widgets/common/widget.js:928:34)
at changedProps.push (src/client/app/widgets/common/widget.js:710:24)
at this.updateLinkedPropsWithNesting (src/client/app/widgets/common/widget.js:382:17)
at linkedPropChangedCallback (src/client/app/widgets/common/widget.js:329:21)
at this._listeners[evt].slice (src/client/app/events/event-emitter.js:29:29)
at this.checkLinkedProps (src/client/app/widgets/common/widget.js:722:26)
at this.updateLinkedPropsWithNesting (src/client/app/widgets/common/widget.js:382:17)
at linkedPropChangedCallback (src/client/app/widgets/common/widget.js:329:21)
at this._listeners[evt].slice (src/client/app/events/event-emitter.js:29:29)

I try to make a lighter session with only this mechanism and it's work fine..
What would the correct way to prevent the crash?

  • OSC version: 0.48.2
  • Operating system : Window 10

Thanks.

2

I'm having trouble understanding this, it would really help if you could upload a session file that produces the error.

3

You can find a session with the bug and another without the bug. The difference is only the variable on the tab "set_preset_0_2".

Preset_don't_work.json (88.6 KB)

Preset_work.json (88.6 KB)

4

Thank you, the bug had been here for a while actually it but was hard to track. It’s now fixed in git and a patched release will be uploaded soon.

5

I test the commit, and it’s work fine!
Thanks a lot !