zl.reg bug ?
I found a surprising culprit (at least for me) on a buggy patch...
it was zl.reg that cannot save the message "bang". nothing about that in the help file..
it's a little bug ?
Without a patch its very hard to see what the issue exactly is. All i can think of is why would you? And "bang" is a keyword in Max, it's best to not use them. In this case i think you just send a bang into a cold inlet which doesn't do anything
<pre><code>
----------begin_max5_patcher----------
475.3ocyUE0aaCBD9YGo7e.wydQFbbly9qLUEgcNkQkCXA3trUs+6ybXZqRS
xnUNR6Eeh69ve22cbvyKWjQazm.Kk7Mx2IYYOO5IC848jEcjQOJN01IrHP5Q
vZEG.Z9TPGbxgAZDpCu3s2.VP4DNoVsqSpfV8fBwwiPTCGkpNvYO2qdvEcyh
tk6QNzMO9EV4qrHbs+PpNry.stfLJ4aVUjSXrRuorx+kyWUPdHtovu28qdHr
CJk7.F5OKW3sil7YtZ7okJ+lRcMCU2W25MUE2Yo1L3bZ0k0D6CnohaoId0jl
pQy532anIrR+Z7dgQbDbfYGnDMcHphOsnUvOGS522dcjFx0awWobvuP4nNkp
QIG6v7D5vgj5kpxc3f8LbttJkI3Jzv2tp5tdr9Zc3e2sx.eLodo9aYB8W1Vb
BtrNkI37+Klh4oHK1ccHNfl5eb47mvvbxG3rJgUOXZiTFeKg7l7ZOXcRE9p0
aPUE.c8Zdx7UmBc9aHmQ9X+S93ATy.eIUNqmM4wSgtxYitpTo68EyoCqh99m
.icZGAlFmOeTa7qqyCqkpv5Mg0F3IYbKgYQpvLNy4FG3FLXBROsYMcZ258fQ
MHQzid7Z0SMdEfZbpx1KBpBupX4hQ.+EWDeN6.
-----------end_max5_patcher-----------
</code></pre>
it was simply that I thought that zl reg could store anything.
"bang" is not a list. [zl.reg] would store "ba ng"...
Bang is a list of 1 item
................
@Schlam: bang is a special message in Max, which doesn't correspond to a data like an int or symbol, but is more like an event flag. You need to escape it in order to not be considered as a bang .
Similarly to what Source Audio did:
Ah right! The escape messages(/symbols?) Hadn't thought of that, nice one! I just resorted to trigger as always...
"Bang is a list of 1 item"
No, Max will consider that a regular bang. For example you can use a trick to have a message sent with a bang right after by seperating it with a comma: [importmovie, bang]
And like i said it gets messy when you deal with keywords in a programming language as they have a special meaning.
<pre><code>
----------begin_max5_patcher----------
623.3ocwV1riZCCD.9bPZeGr74TjcRHD5aPuzS8VaExj3BFQrircV.spu60+
jrP2EBYaHzKwxiGmY977i8KOMI.tRbfpffOC9NHH3Eij.mLqjfVAAvRxg7cD
kSQXtnrjx0vvlE0zCZ2BewHufQzTvO3hZcU8Ic1w3zbQM2oXTqzJIUY9SDMS
vWdYU30kL9Np1YZ7YRMFnULpULqv4GhUa+zrWMcEQmugwWuTRy0dRiwymhBA
Itu3YH6PbxTD3mt876mlXGMCgC+P4qBf+r.Ta3Po.GE0fUD9Z.6VGO+qrmzE
6In6N6kFrHqoum8BVIHAbxc9KfhtLP3K.DtG.kMygUl8aTjkm183+45iUT+F
fvwh0LP1fYMpGrhQK9+CqIvF5RjGLxwndTr5iuY3QF4qVG+sMldU.hjBzan.
EojBGZcZzht3FibrlE6h3XerFMnB0U0Zsf+g76KlhNuS+NsIG06wIse6Hf4x
hNsdEQZNd0T4RJmrZmSKznUwdmRhi5yMNMEtidV7VldZ0dFuPr+CEsekW0Qd
9UIMtyv+hTelZrevkEfSy5jUi+trjnkrCvvQpk08IHG0CzaBxwyF4fLmt23S
umTavmKXltUXvu1IH53nqeK7sRDNGdTefOE66WsnGzeqvteqtWG812n57.6B
u4DRIpk4s++l2N.NyGJnJMi6dw4YJYQCzYm0daunGs8l8nMHpWFL99YvG9Q5
7GrAiQCvfMEIjppmoRUyV71xzuXqPZmmE5my394o94R5yr1s36D.IRSks1TV
WKctH7PZSqCXonfJ40Lm1FIVZsl10RhatxVUQ7b4Zc8zDiB+AzVxxbF
-----------end_max5_patcher-----------
</code></pre>
Yes. You are right, I would like to say that a list can have a lenght of 1.
And I didin't thought that the cold inlet of zl reg can do another thing that just eat whatever you give it.
Thank for clarification !
bang or whatever message should be accepted as input to 2nd inlet of zl.reg.
that because it has no "execute" message function.
also message zlclear to 2nd inlet of zl.reg should not wipe it.
at least that is what one should expect after reading descriptions and the rest.
why should left one accept bang as initial value ?
it seems there is a kind of [tosymbol] inside zl reg when it's feed by first inlet ?
and yes, I don't understand why "bang" is not view as a basic symbol in an inlet that ony accept lists, even if it's a "language" message.