Route and select object questions
I’ve been looking at [route] and [select] a bit recently and noticed a few quirks, just wondered if anyone could shed some light on the reasons these oddities occur.
Multiple matches do not preserve right to left order of execution.
Floats will match a (truncated) integer argument.
Lists (beginning with a number) that do not match any arguments will only send the first element from the rightmost outlet, the reference suggests the whole list should be output.
Here are some examples. Please feel free to point it out if I’m overlooking something obvious!
----------begin_max5_patcher---------- 638.3ocwXEsihBCE8Y3qnoO6Znk1BtuseGalrAkNZ2.EBTy3tSl+8ssnKN5H kQ6.wHJk5smy4d681quFF.WWcf2BAeG7SPPvqgAA1gLCDb79.XY1gMEYs1oA WuWopjvEcOpNSsYmPt8WM7MpNyPVQWFs.fhhLef++UvSG+Mx8kBYAWYsGpev p8pKGUjaWyp0+9aX1o0radp+Ty6VP35L4VH3IySeKLzbYwHISIusMaK+jkU7 CVR.iWRbyPZp4ZLdIUy1zyH3yURkLqzBO3OZDYEvOh53AotwHsh+ZMBBqWoq UDxMUj6SMj7Wz18JwnkWnoNH1shjXUDJ9JW9CoH3wqH3giQVbuJyshSvCnIw QLiNPhl2nDzpoIJotQHUfmq123VSPjz9MP2SfxGm0HZ7hRBz2LWsqgyGh53U VpisJ.iNaTm4ep+R0PDmh5pGPr9b1rQbp2IdkbPOdhkwo1zgzjYi2DOx6FMD 3.C2wlWt2pyh5b9q7K8oim9w2N+2hKd60ZCHs.U0nK6vACcXBDyFePh6KfNK kIvdtLwsjkZdViVYhGTT5NNQmlzkpbVzjnIRSPNEDBqWPHIykfj5Y8vcuDVZ uxucR7UzHwPkIFZyeDtmfwj4pDgOqPbragr55BtSOKyluKwyGFZ7MLf9j8KX wGrPHurmYKCMi+dAqUeb3MmL4od1.8zLm2pDxLkPuK3rIge2j1Ixy4xy8nkh 75Jcj0QPbiH1QiI7XvDaRwjoqEmXxTZeJwT7XvTxziIjKLwldLgcgI5zioXW XhLsXZL66PeNHgRPl+nAVWuVzSe+QQZzW.R08C5ejl5ef9nZ2HPDaxQjqTFO xNA8MuE9O.koUPB -----------end_max5_patcher-----------
It looks like I’ve solved one of my own problems.
[select 3.] will not match "3.4" whereas [select 3] (without the decimal point) will.
Quote: email@example.com wrote on Sun, 08 February 2009 03:51
> It looks like I’ve solved one of my own problems.
> [select 3.] will not match "3.4" whereas [select 3] (without the decimal point) will.
Do you understand why this is so? Understanding int/float behavior in Max is absolutely essential to being able to work effectively.
If you’ve grokked it, then nobody needs to explain what you’re seeing (yet again.-) But if you haven’t, you need to.
Thanks Peter, but I’ve got this one! It was just me not realising that it was neccesary to specify that the argument was a float.