What I will never understand about poly~
Jul 14 2012 | 12:51 pm
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.
- Jul 14 2012 | 1:03 pmit 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.
- Jul 14 2012 | 3:58 pmCould 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.
- Jul 14 2012 | 4:17 pmyou´re right, that doesnt explain why it is not implemented as if.
- Jul 14 2012 | 8:04 pmAnyways, 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
- Jul 14 2012 | 8:40 pmAh, thanks!A very primitive method of working for software in its 6th incarnation, but I'll take it. :)
- Jul 15 2012 | 2:20 amgood idea woyteg
