Julien Vincenot

I noticed more and more recently — patching by myself and watching others debugging patches in Max 8.1.1 — that sometimes #1-like (pound-sign) arguments get lost while editing in in-place mode.

I mean by that : sometimes copying an object with arguments containing those variables — redirecting the #1 to a lower level — the variable symbol gets replaced by its content (in the local instance) when saving.

For instance I copy an object called [my-abs #1 #2] to another place in the same patch or another patch — so definitely in edit mode, where they look like #1 and not like data — and then later the original patch ends up containing [my-abs toto 440] instead, and nothing works as I expect.

Is this a known behaviour in Max 8 or just result of bad practice? Anyone else ever encountered this? Any suggestion how to avoid it?

Hi,
I noticed more and more recently — patching by myself and watching others debugging patches in Max 8.1.1 — that sometimes #1-like (pound

pound-sign-arguments-error-mistakes

Customer feedback helps companies understand the experiences and needs of their community. Here are several ways to collect your customers' insights.

https://customerfeedbacks.info/ 
     Customer   feedback helps companies understand the experiences and needs of their   community. Here are several ways to collect your customers' insights.    

Pound-sign arguments error / mistakes?