Bug in Poly~

Oct 11, 2008 at 6:11am

Bug in Poly~

This one is extra fun! Luckily my poly only has 24 instances, and not 1023.

Anyway, if you have a poly~ object referencing an open max patch, and that patch has a subpatcher open, upon saving the patch, you’ll get X windows of the subpatch displaying on your screen – locking up your computer while they spawn. X is the number of instances your poly~ object uses.

So, I have patch “Zebra” with a [Poly~ moose 24] open. I have the file “moose” open, and am editing a subpatch (“monkey”) in “moose” – when I save “Moose”, I get 24 copies of the “monkey” subpatch displaying on screen.

(also sent to support@cycling74.com)

#40280
Oct 11, 2008 at 6:23am

Actually that’s a feature. You need to close the subparcher before
saving the patcher unless you wants your subpatcher to be
automatically opened on startup. Please do not cross post on support
it is not necessary.

ej

On 10 oct. 08, at 23:11, mushoo wrote:

>
> This one is extra fun! Luckily my poly only has 24 instances, and
> not 1023.
>
> Anyway, if you have a poly~ object referencing an open max patch,
> and that patch has a subpatcher open, upon saving the patch, you’ll
> get X windows of the subpatch displaying on your screen – locking up
> your computer while they spawn. X is the number of instances your
> poly~ object uses.
>
> So, I have patch “Zebra” with a [Poly~ moose 24] open. I have the
> file “moose” open, and am editing a subpatch (“monkey”) in “moose” –
> when I save “Moose”, I get 24 copies of the “monkey” subpatch
> displaying on screen.
>
> (also sent to support@cycling74.com)

#142318
Oct 11, 2008 at 7:03am

Really? It just seems so… bug-like. I mean, what if someone forgets to close a subpatch on a 1023-instance poly before saving? You’d not only have to wait for them all to spawn, you’d have to then close all of them, too.

It’s not that they open on startup (though I guess they will, from what you’ve told me), but they open IMMEDIATELY after saving the poly patch, if the poly object is active in another patch.

I suppose I could see it being useful for when one loads a patch and wants access to the subpatch – though they don’t cascade, either, and there’s no easy way to know which instance you have active in which window. Yeah, you could code one, but you could just as easily code the subpatcher opening on loadbang, too.

#142319
Oct 11, 2008 at 7:22am

Well it has been working like that for a while now and it is probably
not gonna change soon. The fact that they reopen after saving the
poly~ is just because the poly~ gets reinstantied so it’s the same
thing as reopening the patch. Now hat you know that it is a feature
you can rely on that and you’ll get used to it.

Cheers,
ej

On 11 oct. 08, at 00:03, mushoo wrote:

>
> Really? It just seems so… bug-like. I mean, what if someone
> forgets to close a subpatch on a 1023-instance poly before saving?
> You’d not only have to wait for them all to spawn, you’d have to
> then close all of them, too.
>
> It’s not that they open on startup (though I guess they will, from
> what you’ve told me), but they open IMMEDIATELY after saving the
> poly patch, if the poly object is active in another patch.
>
> I suppose I could see it being useful for when one loads a patch and
> wants access to the subpatch – though they don’t cascade, either,
> and there’s no easy way to know which instance you have active in
> which window. Yeah, you could code one, but you could just as
> easily code the subpatcher opening on loadbang, too.

#142320

You must be logged in to reply to this topic.