I'm not clear whether initbang's banging whtn a patch is opened should be regarded as a bug or not.
For my use, it is not a bug.
It is a very useful behavior. It can be used as a [loadbang] or bang when the abstraction is dynamically added. For the malinette framework, it allows me to have just one [initbang] for each object.
Best,
Jerome
Fair enough, I can see why it would be useful.
In case anyone else wants it, here is what I've been using to block iemguts/initbang when the patch is opened for editing rather than loaded as an abstraction. It's just a closed spigot that opens when $0 produces a value for the parent level canvas. Mandatory creation argument specifies the depth (usually 2).
To: pd-list@lists.iem.at From: abel.jerome@free.fr Date: Tue, 24 May 2016 10:37:35 +0200 Subject: Re: [PD] [initbang] in Pd.0.47
I'm not clear whether initbang's banging whtn a patch is opened should be regarded as a bug or not.
For my use, it is not a bug.
It is a very useful behavior. It can be used as a [loadbang] or bang when the abstraction is dynamically added. For the malinette framework, it allows me to have just one [initbang] for each object.
Best,
Jerome
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
-
Jérôme Abel -
Liam Goodacre