Where is the node edit button?

[Lindon]

@Christoph-Hart this sounds like a really really good approach - but your instructions are still leaving me (and I guess others) with a few questions...perhaps a quick step by step walk thru (with pictures for us less literate types) would be helpful?

[Christoph Hart]

@Lindon A video would be best for this actually. We can either mark it as a topic for the next meetup where I can go through this process or David can make a quick tutorial at some point but I guess that he knows about as much as you do. There are quite a few UX improvements in scriptnode that I have sneakily committed a few months back after the feedback from Aaron:

• local cables
• custom node templates
• locking / grouping containers
• parameter handling improvements

There was a long topic where we discussed this stuff but I think it got lost in the noise and with the forum search being as informative as the next drunk guy, we have to accept what we cannot know.

[d.healey]

@Christoph-Hart said in Where is the node edit button?:

David can make a quick tutorial

Seems doable

[d.healey]

@Christoph-Hart Assuming I understood the mission correctly, I think this is the explanation

[orange]

@d-healey Thanks for the video. There is no problem for newly created networks anyway.

The problem here is that the networks we created with the Hise commit from a few months ago cannot be opened and edited in this way. The compiled (or not compiled) custom networks doesn’t show up in the list like you load in the video.

The new improvements doesn’t seem to support backwards compatibility.

[d.healey]

@orange Ah I see, so it's only an issue for previous networks. What happens when you try to open the xml from the old network?

[orange]

@d-healey The compiled (or not compiled) custom networks doesn’t load.

[d.healey]

@orange Can you send me one of the XML files that doesn't show up?

[orange]

@d-healey Ok, I will send a simple example project tomorrow when I sit down in front of the computer tomorrow morning

[orange]

@d-healey I think it was a glitch and it didn't work. It works now.

All we have to do is completely unload the old network that contains the custom network and select it directly from the list. This method is much better, congratulations @Christoph-Hart

I used to avoid clicking the unload network button before, but now it seems like this button will be used a lot haha :)