Loving NC so far, however one issue I’ve found could have the potential to be frustrating and I’m wondering if there’s a work around. If I make a custom Action and stick it on a BT and then later rename the core class of that action (because I want to organize it better, or make it more accurately represent what it does, etc). The canvas will have an error and it cant be interacted with until the class it’s looking for has been restored.
The only way I can solve this right now is to go into canvases and pre-emptively delete nodes I’m going to change.
Right now I’m only working with one canvas, so this isn’t that bad, but in the future if I have multiple canvases it will be easy to forget each canvas I have a specific action in. It would be nice if the canvas was at least viewable and maybe a big red overlay over a node that isn’t working so I can go in and remove it after the fact.
Unless I’m missing some other workaround or best practice for this.
There is a bug in the last version live on the asset store that causes this. Normaly if you change a class name, what happens is exactly what you suggest here. The canvas is still viewable and the missing/change types have a red name to inform you about the fact so you can go in and replace them, but the bug in the current version doesn’t let this happen.
This bug has been fixed though and the new version the the fix is already submited to the asset store and will hopefully be available within the next few days.