Attribute-mapped Inlets don't forward numbers

[tap]

Currently they only forward signals to set the attribute values.

Need to handle this in the number message wrapper?

[tap]

Probably somewhat difficult to do this. Consider the case of an ADSR:

you want an int message to toggle it on and off. you want floats for the various attrs. but if you receive an int at one of the attr inlets then it should be converted to float. but the int message in your object then needs to know that.

this seems somewhat hopeless. I'm going to promote this to a documentation issue for use of attribute-mapped inlets.

could be nice to have the message handler in the inlet as a lambda though... hmmm...