[maxmsp] "sel 0" bug?

sel 0 != sel 0.

sel 0 is looking for an INT, not a float.

On Aug 2, 2007, at 4:19 PM, Matt Wright wrote:

>
> I find it bizarre that passing any floating point number 0. <= x <  
> 1. to "sel 0" puts a bang out the left outlet:
>
>
> #P window setfont "Sans Serif" 9.;
> #P window linecount 3;
> #P comment 187 39 60 196617 Anything over 1 works.;
> #P comment 97 44 60 196617 These don't do what I expect;
> #P window linecount 1;
> #P message 212 82 37 196617 1.234;
> #P message 181 82 23 196617 1.;
> #P message 125 84 23 196617 0.7;
> #P message 98 84 23 196617 0.5;
> #P message 40 81 14 196617 0;
> #P flonum 109 189 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P flonum 87 127 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
> #P button 87 188 15 0;
> #P newex 87 158 32 196617 sel 0;
> #P comment 20 61 60 196617 This works;
> #P connect 9 0 3 0;
> #P connect 8 0 3 0;
> #P connect 7 0 3 0;
> #P connect 6 0 3 0;
> #P connect 5 0 3 0;
> #P connect 1 1 4 0;
> #P connect 1 0 2 0;
> #P connect 3 0 1 0;
> #P window clipboard copycount 12;
>
>
>
>
> On the other hand, "route 0" does what I would expect.
>
> -Matt
>
> _______________________________________________
> maxmsp mailing list
> maxmsp at cycling74.com
> http://www.cycling74.com/mailman/listinfo/maxmsp

v a d e //

www.vade.info
abstrakt.vade.info



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.cycling74.com/pipermail/maxmsp/attachments/20070802/10f70fe6/attachment.htm