Automatic dependencies implementation when copying nodes between documents - nightmare

vvvv gamma feature
1

From a hardcore gamma developer point of view 😅, it’s really important to handle dependencies carefully, especially when dealing with multiple interdependent documents in the same library.
the feature of auto-implementation of packages on node-copy is really causing troubles.
I get it, it’s for beginners who don’t want to be presented with red nodes while they play around and steal from help patches, but for a programmer it is a nightmare 😱.
wouldn’t be possible to add an option in the settings to disable this feature?
thaaaaanks 🙏

6 Likes
2

Totally agree. After weeks of patching, you want to export, and you’ll find the weirdest references in VL docs, and you have no clue when and where it was added. And you also don’t know if it is important to keep or not…

Should definitely be a setting so library devs can turn it off.

2 Likes