I have a quite complex project made in vvvv, consisting of many subpatches/modules. I work on it on two different computers. Several optional values used in several of the subpatches are different for the two computers, Midi ports also - so a decent way for configuration was needed. So I can have different config files/patches for different computers.
Thats why I created a “config” patch. And I made it a module to be able to use it in all my subpatches, which are usually modules too.
Is there a structural weakness? Should I have used custom modules only for basic tasks, everything else as subpatches, placed relative to the main patch??
What is generally a good programming technique for configuration in vvvv?
Enums for MidiPorts (outputs of the config module) get mixed up / are not constant.
It’s the same config module I use in several patches and only its output pins are used (I even dont want input pins, but cannot avoid those). The IOBoxes in it have the same value no matter where I use this config module, thus they are project-wide constants (thats what I need). But the Enums-Pins for Midi Ports of this module have different values in every patch I use the module. And they confuse their values everytime some-Midi-thing changes.
And how to clean that enum problem?
Thanks for any help,