Or [loadbang] could have a second outlet for init bangs...
On Oct 22, 2017, at 7:35 PM, pd-list-request@lists.iem.at wrote:
I can think of an easier solution that doesn't even require another Pd object: [loadbang] could take a non zero argument to turn it into [initbang]. That'd be so easy to implement that even I could do it... (it's just action = LB_INIT instead of LB_LOAD). This would also be backwards compatible, of course. I could even go ahead and make a PR for that.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
I've been thinking about some sort of such extention of loadbang - also to allow you to specify the message, as in "loadbang 5" - I think that would get a lot of use. But I don't have a solid sense of what the design should be (and am always afraid of implementing something before I understand all the issues; if I do something stupid then its there forever :)
Miller
On Sun, Oct 22, 2017 at 08:44:25PM +0200, Dan Wilcox wrote:
Or [loadbang] could have a second outlet for init bangs...
On Oct 22, 2017, at 7:35 PM, pd-list-request@lists.iem.at wrote:
I can think of an easier solution that doesn't even require another Pd object: [loadbang] could take a non zero argument to turn it into [initbang]. That'd be so easy to implement that even I could do it... (it's just action = LB_INIT instead of LB_LOAD). This would also be backwards compatible, of course. I could even go ahead and make a PR for that.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
2017-10-22 19:52 GMT-02:00 Miller Puckette msp@ucsd.edu:
I've been thinking about some sort of such extention of loadbang - also to allow you to specify the message, as in "loadbang 5" - I think that would
get a lot of use.
It would certainly do! There is already an external for this though, it is [cyclone/loadmess], I know I use it all the time. It's one of the new ones we included in cyclone 0.3
But I don't have a solid sense of what the design should
be (and am always afraid of implementing something before I understand all the issues; if I do something stupid then its there forever :)
The thing about connecting [loadbang] to a message is that you can at least click the message on the patch while you're working on it to test things. That's also the case with a plain loadbang, but you can just also connect a bang GUI. The thing is that it'd be more annoying to deal with that if you had a message. The way [loadmess] works is that you can just click on it and it sends the message as well. I like that idea and it's easy to implement it in Pd, and it could be useful for a plain [loadbang] as well.
As long as loading messages go, what I don't like about [cyclone/loadmess] is that you can't give it a comma and send more than one message at once. That would be cool and I was even considering creating another external so it could do that.
2017-10-22 16:44 GMT-02:00 Dan Wilcox danomatika@gmail.com:
Or [loadbang] could have a second outlet for init bangs...
that actually sounds better and cleaner, and totally compatible with Miller's idea of allowing it to send messages as well. I don't see how that would raise any issue.
cheers