bug in selector~ in max 5.02?

Sergio Martins's icon

In this patch, i have a selector~ receiving int numbers from a dial object, and i get a messange saying that it doesnt understand floats... can anyone check this out? I did the same patch in 4.6 and works fine...

macbook pro 2.4, OSX 10.4.11, max 5.02

Chris Muir's icon

The problem is really with dial. It seems to always put out a floating point value.

An int between dial and your subpatcher will work around this problem.

Eli's icon

I think this is not a selector~ problem but a dial problem. Dial is outputting floating-point numbers even when outputting whole integers.

A quick fix is to have the dial connecting to a [number] object either inside or outside of the patch, changing the floating-point numbers into integers.

Did the programmers intend for [dial] to always output floats?

Sergio Martins's icon

Ah, thats right, the dial, i checked it with a print...

thank you both for the help,

cheers