phineus

I'm modifying a bpatcher called output.mxb that was created in Max 4.5 - it uses a # argument. Specifically, it has a label that just has #1 in it.

When I open it in Max 5, it appears correctly, the 8 versions of the bpatcher each have a different label, reflecting the value in the Argument for each one.

But if I edit the bpatcher and re-save it as output.maxpat, then update the Inspector to point to the new .maxpat file, now the bpatcher shows a literal "#1" in each label spot instead of the Argument... 

: the other functions controlled by the pound-sgin value seem to work fine.

I've attached the bpatcher here in case it matters:

I'm modifying a bpatcher called output.mxb that was created in Max 4.5 - it uses a # argument.  Specifically, it has a label that just has #1 in it.

When I open it in Max 5, it appears correctly, the 8 versions of the bpatcher each have a different label, reflecting the value in the Argument for each one.  

But if I edit the bpatcher and re-save it as output.maxpat, then update the Inspector to point to the new .maxpat file, now the bpatcher shows a literal "#1" in each label spot instead of the Argument...  But just in the label: the other functions controlled by the pound-sgin value seem to work fine.

odd-issue-with-pound-sign-argument

In max 5 the [comment] object won't respect a #1 type argument. However you can use use it in a [loadmess] for example: [loadmess set #1] and then hook that up to your [comment].

odd issue with # pound sign argument