Hi all,
Just wondering if anyone wrote this as an external, as I don't see why someone would not have. I keep wanting a [route] that has a sort of "set" message where you can change the symbol/value that it looks for to match against. I found Martin Peach's [nroute] in svn, which does exactly this but does not remove the item from the list. For now I am using this and then using [list split] to remove the item, but I imagine someone has found a more elegant solution. I definitely have not using combinations of [select], [unpack], and [spigot].
cheers, Rich
Shoot, I just realized that [nroute] is part of Maxlib, not mrpeach. Sorry.
On Sat, Jan 3, 2009 at 10:00 PM, Rich E reakinator@gmail.com wrote:
Hi all,
Just wondering if anyone wrote this as an external, as I don't see why someone would not have. I keep wanting a [route] that has a sort of "set" message where you can change the symbol/value that it looks for to match against. I found Martin Peach's [nroute] in svn, which does exactly this but does not remove the item from the list. For now I am using this and then using [list split] to remove the item, but I imagine someone has found a more elegant solution. I definitely have not using combinations of [select], [unpack], and [spigot].
cheers, Rich
Hallo, Rich E hat gesagt: // Rich E wrote:
Just wondering if anyone wrote this as an external, as I don't see why someone would not have. I keep wanting a [route] that has a sort of "set" message where you can change the symbol/value that it looks for to match against. I found Martin Peach's [nroute] in svn, which does exactly this but does not remove the item from the list. For now I am using this and then using [list split] to remove the item, but I imagine someone has found a more elegant solution. I definitely have not using combinations of [select], [unpack], and [spigot].
Maybe [sroute], currently in the list-abs collection, is what you want? It uses [select] internally to mimick a [route]
Ciao
Frank
Frank,
You always have such clean approach :) I should look through your list-abs collection closer as I always end up using a much more awkward solution.
Still, I don't see why [route] should not have a 'set' message like many of the other built-in objects, at least for its first argument.
cheers Rich
On Sun, Jan 4, 2009 at 12:31 AM, Frank Barknecht fbar@footils.org wrote:
Hallo, Rich E hat gesagt: // Rich E wrote:
Just wondering if anyone wrote this as an external, as I don't see why someone would not have. I keep wanting a [route] that has a sort of "set" message where you can change the symbol/value that it looks for to match against. I found Martin Peach's [nroute] in svn, which does exactly this but does not remove the item from the list. For now I am using this and then using [list split] to remove the item, but I imagine someone has found a more elegant solution. I definitely have not using combinations of [select], [unpack], and [spigot].
Maybe [sroute], currently in the list-abs collection, is what you want? It uses [select] internally to mimick a [route]
Ciao
Frank
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Sun, 4 Jan 2009, Rich E wrote:
Still, I don't see why [route] should not have a 'set' message like many of the other built-in objects, at least for its first argument.
You can't do that, because then [route] wouldn't be routing set-messages anymore. That's one of the big recurrent problems with Pd: 'set' and other special options conflict with the anything-method in objects that have a anything-method.
An anything-method is a behaviour defined for all messages, except all other defined behaviours. If there's a set-method or anything else, they create exceptions to the use of the anything-method. It's not just a matter of compatibility with older versions, it's also about keeping the rules simple and free of undesirable exceptions and cripplings. Everybody wants [route set] to work (even though many might not realise it yet).
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
Hallo, Mathieu Bouchard hat gesagt: // Mathieu Bouchard wrote:
On Sun, 4 Jan 2009, Rich E wrote:
Still, I don't see why [route] should not have a 'set' message like many of the other built-in objects, at least for its first argument.
You can't do that, because then [route] wouldn't be routing set-messages anymore. That's one of the big recurrent problems with Pd: 'set' and other special options conflict with the anything-method in objects that have a anything-method.
But I think, the approach of [select] with a second inlet would be feasible for [route] as well. I submitted a feature request regarding this some time ago.
Ciao
Frank
On Sun, 4 Jan 2009, Frank Barknecht wrote:
But I think, the approach of [select] with a second inlet would be feasible for [route] as well. I submitted a feature request regarding this some time ago.
I thought I had done that for [route], but I didn't. I only modified [select] so that it has as many inlets as there are arguments, plus one.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec
-
Frank Barknecht -
Mathieu Bouchard -
Rich E