Forums > MaxMSP

loadbang issue when encapsulating

June 28, 2010 | 3:24 pm

When you encapsulate (command-shift-e) a patch which contains a loadbang object, it doesn’t generate a bang (you have to open the subpatch and doubleclick the loadbang object). Ok, no big deal.

The problem is that this happens even if the loadbang object is inside an external abstraction. This, imho, is a problem when patching: if you happen to encapsulate an abstraction with an internal loadbang, that abstraction won’t work as usual, and it could take a while before you can figure out why the patch don’t work…

June 28, 2010 | 4:01 pm

it loadbangs ok for me (save both load ldbng-test)

  1. ldbng.maxpat
June 29, 2010 | 3:31 pm

Sorry, I wasn’t clear. The problem occurs only when patching, i.e. right after you encapsulate the abstraction. If you save and then reload, everything is fine. As I said this can be confusing when you are tweaking a patch (unless you remember to save it, close it and reload it).
I attach an example (load loadbang_test).
NB: the problem appears only when you encapsulate with the shortcut command-shift-e (on a Mac), not if you choose "Encapsulate" on the menu.


June 29, 2010 | 5:33 pm

my guess is, you forgot something important

— Pasted Max Patch, click to expand. —
June 29, 2010 | 6:03 pm

>my guess is, you forgot something important

It doesn’t seem to work.
Does it works for you?


June 29, 2010 | 9:40 pm

my guess was a complete misunderstanding of the problem

June 29, 2010 | 9:46 pm

so… you’re indeed right, with the shortcut for encapsulate it seems that the objects selected are recreated yet not loadbanged (or something like), whereas using the menu command will actually induce a loadbanging for all the encapsulated objects.

June 30, 2010 | 3:55 am

that is weird.

different results from a shortcut versus selecting from a menu? I would have thought these were identical… where else might this problem crop up?

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

Forums > MaxMSP