Yeah, this works, if you want to need a ton of clicks for each instantiation (or make abstractions with various outlet lengths, still "ugh").
Instead, wouldn't this (or something similar) do the job? [list split 1] | \ | \ | [output list data] | [select a b c] Of course, if you want to detect the list and then pass only non-list data, I'm not sure what to do...is there an object like [islist] or something that will tell you if the incoming message is a list? ~Kyle On Nov 30, 2007 1:17 AM, Chuckk Hubbard <[EMAIL PROTECTED]> wrote: > On Nov 29, 2007 8:45 PM, Martin Peach <[EMAIL PROTECTED]> wrote: > > What is [select] supposed to do with a list? Just select based on the first > > element? I think it should reject lists altogether and suggest the use of > > [route]. > > I agree with Martin. [route] is meant for lists, [select] is meant > for floats or symbols. I suppose lists don't work with [select] for > the same reason [route] doesn't have a right inlet, considering what > Frank pointed out. > If you connect all but the right outlet of [route] to [b], you have a > [select] that handles lists and has no right inlet. > > -Chuckk > > -- > http://www.badmuthahubbard.com > > > _______________________________________________ > PD-list@iem.at mailing list > UNSUBSCRIBE and account-management -> > http://lists.puredata.info/listinfo/pd-list > -- ----- ------------ ---- ----- ---- -------- - ------ http://perhapsidid.wordpress.com http://myspace.com/kyleklipowicz _______________________________________________ PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list