hey,
i find myself often repeating a construct like this:
[t b a] | | [1 ( ... |
now, the last time i was using Max, i noticed that Max's trigger object allows you to go
[t 1 a]
and the left outlet will send out the number 1. or even:
[t reset a]
and the left outlet sends out the message 'reset'. this seems to me like an extremely handy feature, so if it gets the blessings of the list(s) i'd like to go and implement it and submit a patch.
what do folks think of this? i know there was some discussion a year or two ago, talking about how you should only be using the 'bang' and 'anything' keywords with trigger and not using it as a type-bashing object. not sure what came of that though...
chur d
Damian Stewart wrote:
hey,
[t 1 a]
i like this
[t reset a]
but i don't like this.
it makes the bfsla syntax less readable: why does [t a b c] output "c" at the 3rd outlet, but neither "a" nor "b" on the 1st two outlets? (for those who don't like abbreviations: [trigger bang this float])
on a related issue: the reason for zexy's pack is that in Pd we can have [pack 12 43] but not [pack two symbols]...
fgmsadr IOhannes
Hallo, IOhannes m zmoelnig hat gesagt: // IOhannes m zmoelnig wrote:
Damian Stewart wrote:
[t 1 a]
i like this
Me doesn't like it too much: Conceptually it clashes a bit with the possibility to replace "f" with a number in [pack]:
[pack f f f f f f f f f]
is almost the same as
[pack 1 2 3 4 5 6 7 8 9]
but the latter is easier for counting the arguments.
And how should [t 1 a] react to a list of "2 3 4": Should the first outlet give 1 or 2?
Ciao