Forums > MaxMSP

Editing embedded bpatcher?

May 21, 2006 | 4:12 am

Is there any way to edit an embedded bpatcher? I can change it back to
the non-embedded and edit it, but that undoes what the embedding is
useful for… No big deal, just curious. I’ve also tried
"thispatcher" with the front message, but that sure enough treats it as
part of the patch it’s in, rather than as a subpatch.

Peter McCulloch


May 21, 2006 | 7:03 pm

Peter,

I came across a similar issue today. I do not know if our workflows are
the same, but I believe I found a bug. Hopefully someone at Cycling ’74
will comment on this.

Problem: The following, from page 74 of the Max Reference Guide, is
*NOT* working with v4.5.7.

"If the Command and Option keys on Macintosh are held down while
clicking in a bpatcher, a pop-up menu
allows you to open the original file of the patch contained inside the
box in
its own window, or change the patch currently contained inside the box in
its own window."

Reproducible: Yes, 100%.

Steps to reproduce:

1. Open a patch that contains a bpatcher.
2. Unlock the patch.
3. Hold Command and Option while clicking inside a bpatcher within the
patch that was opened in step 1.

What should happen: "a pop-up menu (should appear) that
allows you to open the original file of the patch contained inside the
box in
its own window, or change the patch currently contained inside the box in
its own window."

What does happen: No pop-up menu appears.

Workaround: None!

Other relevant information: This happens with bpatchers that are and
are not embedded into the main patch.

B&W G3/500, 1GB RAM, OS X v10.4.5, Max/MSP v4.5.7

-Jonathan


May 21, 2006 | 7:26 pm

try control + shift click seems ok here on latest


May 21, 2006 | 11:45 pm

Hello Dave,

Thank you for your response. It seems that something is not right.
Whether the error is in the documentation or in the program if for
Cycling ’74 to decide.

Control+Shift click produces the same menu as control-click. If this is
the intended and expected behavior, the simplest way to fix this is to
update the documentation. Also, it does not mention in the
documentation that you cannot open the original file of a bpatcher if
the bpatcher is embedded in the main patch. I believe this is worth
noting, as I thought this would be possible (I RTFM before I tried it).

Hopefully Cycling ’74 will chime in on this issue.

Cheers,

-Jonathan


May 22, 2006 | 1:51 am

the only way that i could think would be to copy it to the clipboard. Or, build some ridiculous scripting beast…


May 22, 2006 | 1:17 pm

in 4.1 and earlier it was just control – which
brings the regular object-releated context menu
up where you of course can always edit the content
of subpatchers, abstractions, and bpatchers.

that has changed ? …


Viewing 6 posts - 1 through 6 (of 6 total)