What I will never understand about poly~
Why doesn't the poly~ object automatically update the number of ins/outs when the encapsulated patcher is edited?
When I double-click on the poly~ after editing ins/outs, the changes are obviously there - so why do I have to close the original patch, then reopen, to reflect the changes?
I don't get this. Please tell me I missed something.
it could be that this is intended, because in one point there i a difference
beetween poly~ and other subpatchers such as bpatchers or subpatchers:
the poly object box does not directly reflect a patch loaded from disk into
RAM, but only aliases of it.
or on other words: the poly object box is not representing a certain voice
of the poly.
Could be, but I still don't understand why an intended user change is not reflected in the poly~ object in most instances.
It should at least be a user selectable choice to make this automatic - if possible.
you´re right, that doesnt explain why it is not implemented as if.
Anyways, you can get the new in/output easier by just reloading the poly patch via deleting the poly~ object and hitting command+z, all the connections also will be intact again.
cheers
Ah, thanks!
A very primitive method of working for software in its 6th incarnation, but I'll take it. :)
good idea woyteg