You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the current RC I am observing the following issue:
Sparck2 is a collection of abstraction and can be used inside normal max patches. I am using ossia with for my UI. This is great, since the last working version with sparck was 1.2.4.
So: YAY!!
But..
When loading a sparck patch everything works fine. The node tree is generated and I can populate the nodes with values via a dict like illustrated in your launch-patcher.
But when I load a new abstraction into my patch, the node tree gets rebuild and the previously loaded values get lost. This happens only with the first abstraction - each subsequent loaded abstraction doesn't initiate this.
It doesn't happen every time, only 90%. 10% the node tree rebuild is not happening.
The text was updated successfully, but these errors were encountered:
hey! that looks like an interesting bug. I don't understand why specifically the first would cause this and not the subsequent ones. @avilleret if you happen to have an idea..
launch sparck from the package-manager and press dependencies (all needed stuff should be inside the package-manager - with the exception of ossia and java)
Hi
Using the current RC I am observing the following issue:
Sparck2 is a collection of abstraction and can be used inside normal max patches. I am using ossia with for my UI. This is great, since the last working version with sparck was 1.2.4.
So: YAY!!
But..
When loading a sparck patch everything works fine. The node tree is generated and I can populate the nodes with values via a dict like illustrated in your launch-patcher.
But when I load a new abstraction into my patch, the node tree gets rebuild and the previously loaded values get lost. This happens only with the first abstraction - each subsequent loaded abstraction doesn't initiate this.
It doesn't happen every time, only 90%. 10% the node tree rebuild is not happening.
The text was updated successfully, but these errors were encountered: