sending same message to different [receive] objects

flim's icon

...one by one - a [forward] task?

cheers!

-jonas

Max Patch
Copy patch and select New From Clipboard in Max.

Jesse's icon

pattrforward may be a better approach - no receive objects, clearly defined hierarchical namespace.

Hans Höglund's icon

Or use a single receive object name combined with route.

flim's icon

thanks for the replies! but I guess both approaches won't do - at least not fully (for the [route] method simply loses in its looks, hehe).

I guess I'll stick to my [sprintf] [forward] combination. thank you anyways!

all the best

-j

Max Patch
Copy patch and select New From Clipboard in Max.

Hans Höglund's icon

To be clear, I meant putting one route object in each subpatch. I often use a code style like that to simulate a "namespace hierarchy".

I usually avoid the pattr objects as I believe they have some fundamental design mistakes.

For example:

Max Patch
Copy patch and select New From Clipboard in Max.

I might add that generating symbol names through sprint is necessary in other circumstances, for instance generating unique names for colls and buffers inside abstractions.

I still believe that you should minimize the number of global symbols you use though, especially for receive objects.