I think that having an option in the iobox to force to int would be the best option performance wise (like using the enum for slider/bang/toggle, just add integer there and the iobox stays int whatever happens).
the (original) idea for this, is to ask for an int (as opposed to give one out)
the use of asking for an int, is for interface ioboxes and for inputs on modules
so if you’ve got a module (say you’re making your own linearspread!)
chances are that you want to make one of the inputs an integer (i.e. spreadcount). the problem is that if you connect that input to anything that accepts non-integer values inside your module (e.g. a ‘+’ node) then your iobox starts asking for a non integer value.
this is essentially a UI plugin, a companion for IOBox
Perhaps could make another Int which is for making ints (round, floor, ceil as you suggested)
that’d be a ‘make into int’, this is an ‘ask for int’
(also, rather than connect the incoming iobox to something else, you use the output of the ‘Int’ node, that way iobox still asks for int but all data is passed through)
that’s true. the only comfort is that, if the first connection you draw goes to an integer-wanting pin, it will be integer-wanting again on reload.
anyway, good idea to solve all this hassle with a plugin! :)