[PD] Bug Report/Feature Request: trigger should work like pack
williamahuston at gmail.com
Mon Apr 15 06:33:07 CEST 2019
Someone brought it to our attention on FB, and it seemed like a legitimate
Thanks for remind me that unpack really does guarantee R to L fanout order.
You're right Alex.
It's not really my issue.
I have no real motivation.
I should have left it alone.
I think my root concern at this point is how trigger is overloaded.
if it only dealt with bangs, that makes much more sense.
If you are replicating a float on all outlets,
that seems to me an entirely different object!
That's got nothing to do with a triggee.
That's a float clone, or a symbol or list replicator.
When you add all those datatypes into one object, which you call trigger,
and allow even mixing datatypes (!!) as arguments to a single object (!),
well, IMO that produces some possibly very ugly code which does some really
This is my new request,
and this is "mine" now ;)
Let's decouple that overloaded trigger
into more rational objects
symbol replicator / sequencer.
deprecate existing trigger.
Because I think
*[t b f l s 55] *
is VERY MESSED UP,
and *it's never going to so anything reasonable*, I can't imagine any
useful purpose for that,
allowing it will only confuse people, and make the language irregular and
harder to learn,
and thus it should be prohibited by syntax
or at least deprecated.
On Sun, Apr 14, 2019, 11:57 PM Alexandre Torres Porres <porres at gmail.com>
> Em dom, 14 de abr de 2019 às 21:44, Alexandre Torres Porres <
> porres at gmail.com> escreveu:
>> which one, this? https://github.com/pure-data/pure-data/issues/354
> Anyway, I just went ahead and made a PR for it. I just got the code from
> Purr Data and swapped with vanilla's, nothing else! I obviously tested and
> itt works just fine. I also updated the help file, of course (by the way,
> Purr Data's help file doesn't mention this feature).
> I see how this could be convenient in some use cases, but I don't have
> that much of a personal motivation to request this. I guess my main
> motivation to do this PR is that:
> A) people often request for it (maybe they are influenced by Max or Purr
> Data, who knows, doesn't matter).
> B) I think it's really bad that Purr Data is not compatible to Pd, but I
> understand this is not Pd's fault.
> Well, if this doesn't get accepted, I guess I maybe could make an external
> like it in my library.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pd-list