Hi Luka and team,
Is there a way to use max wildcards with beam objects? I was trying to use it with the tag object
[tag #1_led]
but didn’t have any luck. Let me know if I’m missing something. If not, might be worth thinking about for a future version!
Hey there, Max unfortunately only allows using the wildcards when there is a space after them, for any object, including the beam objects. However, you can concatenate the wildcards with other strings using the [combine] object. Perhaps that is of use?
----------begin_max5_patcher----------
377.3ocwTF0aCBBD.989qfPe0sTvt149qrrzf5kNZTv.XmKM9ee.Zc1LZml0
jwCBb2wwcedGmVfrCbprAz3WPu525FmFVc1.q5KE5UTxZxJXZ2gwo0FiTfi9
oUULS16bw9cJHy3tGDca7iqhPjjmcSz0m+hdKvw44N2KSO7vlPdWVaJ.i4yJ
v6ZbJSrGGzQULEqDLfZGHXoEN6WEvLQcIWXcoKqHg02cmdCtPe6vt1n+DLKA
slsGBkuFnwAQ7RxtBHeh7dM0i3sdd+zJ+F5ux63ov6vrdLDo+SPT.eXyhawv
LYYJW.nkDzLfYWwKMNwMkrchvjLIXFcW.J8Z.0up283Bapey9det6rJLq0xZ
UVef22dhBSgbPa3BlgaefXvbRm4y9e+LiJx7hJaMOhb8n5B.xppNBJc24+NT
rEgGjJqnjnQx3BurQunfUvQd+oG8PDlorUbFa4VsxkG3lMqwi8jLGThZ9PiS
Opv9Beg8INcEyS.eaxh1urFoBkI
-----------end_max5_patcher-----------
Hi @mbdaily,
Besides what @Mattijs is pointing out, [beam.tag] indeed cannot directly initialize with an abstraction argument as a tag argument of the object itself, such as [beam.tag #1].
However, you can achieve what you are trying to do by setting the [beam.tag] object’s @tag attribute using [loadmess] or [loadbang] in the abstraction:
In combination with the tip from @Mattijs:
Oh, thanks that’s perfect; I didn’t find documentation about the tag message; I somehow thought it couldn’t be assigned dynamically.
But about the wildcards, maybe we’re misunderstanding each other, but you really can concatenate wildcard with other characters as a creation argument (but has to start with the wildcard):
(unlocked patch on left, locked on right)
You’re right! I was almost sure this was not possible in Max, but for some reason I didn’t think to verify that.
That’s so weird that I had it so clearly planted in my head that this didn’t work. Perhaps this was a recent-ish addition? Anyway, thanks for correcting me, this is indeed perfectly valid.
Oops, I knew this was possible with the unique identifier #0 and --- in M4L, but wasn’t sure it also worked with patcher arguments, good to know!
