It's not intentional.. and I can't see why this is happening.
Anyway, I'm sorry to have to ask this, but where can I get eh new initbang? (Deken doesn't find it, hmm...) I can't test without it.
thanks Miller
On Tue, May 10, 2016 at 01:52:07PM +0100, Liam Goodacre wrote:
This behavior is documented in the help file, so I guess it is intentional.
Another change is that [initbang] now bangs when the patch is opened, whereas before it would only bang when the patch is called as an abstraction. To change this, I've been using another iemguts object, [dollarzero], to call the $0 value of the parent level patch. If it returns a bang, it means there is no parent level patch, and a spigot is closed; if not, it is opened. It works, but it is a bit of a hack, and it would be nice to see the original behavior reinstated.
To: pd-list@lists.iem.at From: zmoelnig@iem.at Date: Tue, 10 May 2016 12:08:53 +0200 Subject: Re: [PD] [initbang] in Pd.0.47
On 2016-05-10 12:04, Jérôme Abel wrote:
Hi,
I notice a "new" behavior of the [initbang] object. When I put directly in an abstraction, it sends a bang, but when I put it in a subpatch into the same abstraction, it does not.
Is it the new and fixed behavior ?
confirmed. i'm not sure whether this is intended behaviour.
fgmasdr IOhannes
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list