you could use preferences files in txt format, whose names are bound to an argument to the abstraction.
the [text] object works very well for reading some data from a textfile on loadbang.
in case you also want to use diffetne objects in your abstraction, you could use scripting to delete,
create, and connect different objects, but if you exaggerate that, creating the abstraction will be
too much work and making and calling that an abstraction will become pointless.
Yep, no problem. You see, I was trying to build a [route] object which could have its number of arguments (and thus, inlets and outlets) changed dynamically. I assumed that the best way to do this was to use [bpatcher], and update it (save it) each time I changed the route object. I found a much easier way around this though:
I simply did the work in the main patcher.
I created each route object via scripting/[thispatcher]/etc. and used [prepend/append/uzi] to add the number of arguments dynamically.
I deleted each expired route object once a new one had been made.
I then used the sendbox feature to move the route object to wherever I desired on my patch.
Finally, I connected all of the objects dynamically.
I’m not sure if this will be helpful to anyway, but it can’t do any harm.