libossia
libossia copied to clipboard
Wildcard syntax with comma does not work when declaring addresses in messages
Max automatically adds space in messages when not surrounded by comma. This leads to an unconvenient/clumsy way of declaring multiple addresses. Not completly a bug since it is documented ("avoid spaces"), but could maybe be improved/simplified if allowing spaces. See patch below.
----------begin_max5_patcher----------
2074.3ocyZszbihqEdsyuBUrY131CR79tZ5Z1cu8slp5scOkKAnXqtAgKjbm
jIc9uO5AfAGyijFbxhXGKARmuuyCcjz4waVYEWbOgaA9Ofu.Vs5waVsR2jpg
UU+dkUN99jLLW+XVIE44DlvZsoOA4dgt86JKX6pa8.Vjrmx1ssjjHLid.Zi8
Z.xyQ8kq9SmnM1f+t5UXGyKNJxHB8zXW0Z7w33LBmlRTshpZklpmxh3u8ATf
UmGU0A7zPRY0iHT01S2bi5i0SDq4DNGui7LrhSSKkcAd7iqAwqA7hbxZfPAX
9SCPA9PMED4q9B5Eo+EpWNnFFllDObfXFFKqlWnMQ3acIXidEvtOUrDgbvcE
keW94dBCjRjuSIIEjRUfL6A.kIoABPJOJPWyDRtRNbXAsfsMixHIEGY5Qzoe
tBgPFSDmMdRVJvVSVtiZvzlQbWPSiWqafiMTCHWWEf7BeEvx4M.V+0+a.L4Z
bpqvjqyq.SnEDSLxcx43YPRZVdfvRAUNyCfOTf1U0wQaDFMu9sPOq4BnwGEh
B1P.IztkhB4NhhpWfDik13WDLAml8RbNQPJ2RX3JMp8BqQ4GJoLwsxvxe8qq
ik+oBLK+Z7HyUZXTjNBMzYlCMaa8twV10n0WHaY2qmsrKxagskguGrk4OnPw
qvjtRQWaRGBmUMcn00JGq7G1xkvayivMa7d524EGKSH5e47zuuCSYad7S+7y
+7O+4m3+7y7m.+gRzA5NT4ZfK+0RCwr.ss1Vy01dVIwfYKisdLhJ3bJdSdQJ
IC7+OlInGj4RC9iTBOojdPQDfuZ8QfF2jR9oD5vb.FneuuZIYT7Nod.e+dR1
A4yjWTOQcXQz.496F0xW0w0jZm2LQidKdzUvNhXKSFCPZIlPrFGngAlu7mU6
knKauzVbHkUvqBeqrtklQ9gT4JU1slwUV3CGZ07pVuhhT9VgdfBW2zDkYZB1
zTI4Gz522uoUbojTDRF4XoFLV26WupfZXj1TkrizFMjV8TIRZEwIZVuLfTeU
28IZ1yVSrQlcQ5q+x2tk8jTQuKqH46jzVwpkzrbQRJqcffNcmRtEK8R1daAS
vo+iIKTks5E5+1JI7hcpvfV7+XIEm0.fckzzBlRH5nITMWOceQtuPytCaCF8
SvvGtvKa1pUOcxkf7HOFWpTTUKbgp6TTTj0sql2Kibqnp6CTF6LVTTbn+NKo
61Ov6FWH6LenwV2Ce6Qlo2sRaBwVN9GcYaANKqxas6veOlQywBhfZTAH6lNM
KduWF6qHKqCdM87iKzSpzFOgbGMUrWOQsMFZBhpU0MZ4T5NBWzsMUDztsvEO
XH8VMcLtxGdqfjeHShhtOfz6fxE78E2wqdvZCs1DvoiyosOc6PecZevki6FG
LIStbJPx7s68BQAg95MsCM9mdOaQy9CDNRvv9BH1yhnqpWAnJLyqjR5rpvky
6lSDp+FgWPdtJdww09TzqEgWB5kWfWWdANFi3aqOMjHcPOeuEiQ7eqYj+ICv
yjgRFkRbzmOjCJR6BYOEmGzfTx5AnEu2QNPiETwyPLQ5bHCbWLSEzUwTQOpi
.YOeMh045X1ut5yYGvvdArcqNpOYv1qHoGHVJ49qnij.jAhGi3LdMliwwYVb
g5bLAmyfNv2KAbG2Ox08J4FE9dgSrGKxRH75rHDJ3cjYxKHj6hmuB5Me4YIc
.hAeXrEmgtAJFwbCd9ASfPblTfk0pEDD8yOdu07i9TdHkiQOQ5UrpB75Cm.+
3ND+n3j0UovLFE41KE4ccnnRo3S.meJQCuDEzSG.FZ6rno4AuN44MkbZp7fV
7jZbbmmrZlS9wH8ik+ule7rQSlfr6gAFHnwuZdcmNZJ0Q.2yANnAmp+KSMlS
xuROVsadPWblR3BJq4f59xIfodvIoYdoBQvDEBzBJC9STFBVPYvap7P3BKDv
2XkgJPxzXhkzrTsCiIIEKtPLI8g6BJE0VbuswIPSNPg+RJE9uGbSQS0OMZoE
BzTMNcVJoXpQKdthqnL0b6c1usR1ErraDM3xHZuGbngScEu5PwKiTLQg.1OU
T0X80pZot6rzsl6IbKVHJowxMpvO+dheQ2m0trhXb1YWB0kttqaNIbyTcg7R
tFdSYaD3LuE4zrU0FeiJ1jPxxhUWUc8n168GO.PcbzkohSUI+DF1KTcaMKmc
E1xcBj0ofBdFcjQ4c1O9koml5PVNdMWbJx0t0L+7KW2p00xV2TYwcl8uaOTY
OHmkTxsFITt8x0.e+0puz6b5zGlpf5xM+AX8ef+138LSUM6elQS9N32ZLY+M
PkUMPT.3DBXewc.VQJAPYbAlkP3pRMAjTRvBR5EKyFmKYm7Irb.+LY2wrS06
joRZUxRNtbG0TY.18aK4YphWXno.DL0thu6KrD8cZwARUiolQ9hjrcV25CXq
Qs8VVirF1J45UcvlRmpox+dM0TpwmLx0bW3nQBB0qWWudZnVNZm3YHxyMRQy
AQ91Agp+KLxEBC6x58xa5mn615Mz34KkUQlijS536X6Y5qoNQAWo4A5dslHu
q0DMIpydFlo5AYvYpcxLudLAmvLENCST3TPj6LLQQSYh55rkSSOTPYhJW2.u
P8gsZpor1+5WTzlhgZzbnTm37.GgAPNglxo.407ylWo6FuVTYsKu0caUch+d
V0YplyypJyypHymWMl8WIlmWEl5sJXpHsyh42jfw+EmWji2tmtSRE61KT6nn
DypyOut5G6RQ3jDYVQsVcBZx6x6TxW01Gqqn5R4KbdowYkqJc4ZETMC0Swhd
yS27u7k5QF.
-----------end_max5_patcher-----------
what about using |
instead of Max special character ,
?
i.e. address {A|b|some|things}
in a message box works fine.
@avilleret Good point. Meanwhile, I think it would be worth preventing wrong syntaxes to create weird namespace (like "_A" <= why that underscore?) or better, to have the object smarly support this, if this does not clash with any other messages.
Max adds a space, libossia replace space with underscore.
We could trim leading and trailing spaces to avoid "_A".
And yes we could also try to handle comma but since Max split message with comma I doubt it will be very useful. At least I prefer using |
despite it became quite cumbersome to type with macos.