Cycling 74 » Topic: What I will never understand about poly~

What I will never understand about poly~

oivindi — Sat, 14 Jul 2012 12:51:14 +0000

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.

Re: What I will never understand about poly~

Roman Thilenius — Sat, 14 Jul 2012 13:03:44 +0000

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.

Re: What I will never understand about poly~

oivindi — Sat, 14 Jul 2012 15:58:45 +0000

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.

Re: What I will never understand about poly~

Roman Thilenius — Sat, 14 Jul 2012 16:17:50 +0000

you´re right, that doesnt explain why it is not implemented as if.

Re: What I will never understand about poly~

woyteg — Sat, 14 Jul 2012 20:04:04 +0000

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

Re: What I will never understand about poly~

oivindi — Sat, 14 Jul 2012 20:40:46 +0000

Ah, thanks!

A very primitive method of working for software in its 6th incarnation, but I’ll take it. :)

Re: What I will never understand about poly~

Roman Thilenius — Sun, 15 Jul 2012 02:20:15 +0000

good idea woyteg