If you save a subpatch with a space in the name AND a category/tag, the patch will work and save happily, but will not be found and come up red on reloading the patch.
Works: “Sub Patch.v4p”
Does not work: “Sub Patch (Value).v4p”
To duplicate, create a sub patch with shift-ctrl-p, then go into that patch and do a save-as giving it the above name. All is well and working.
Save the parent patch and quit. Reload the parent, red node, does nto show up in browser.
Here’s the fun part: even dragging and dropping the patch back into the parent will not make it recognize it. The dropped node will be added OK, but the existing one stays red with no connections.
subpatches and modules are not supposed to have space in the nodename.
vvvv could of course warn you about that but as long as it doesn’t just consider the behavior undefined when you don’t follow: conventions.nodeandpinnaming
Yeah, it was just a thoughtless keystroke as I knew you shouldn’t put spaces in node names, but vvvv should not happily accept such a name and continue to work and break when the patch is loaded later.
It would be nice to flag it, either when doing the “Save As” (best) or when saving a patch with subpatches that violate it. Note that a top-level patch can have spaces in the name and everything works fine, so there is a bit of an inconsistency. Thanks joreg!
