|
|
Jun 28, 2010 at 3:24pm
loadbang issue when encapsulating
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…
|
|
|
Jun 28, 2010 at 4:01pm
it loadbangs ok for me (save both load ldbng-test)
|
|
|
Jun 29, 2010 at 3:31pm
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.
m
|
|
|
Jun 29, 2010 at 5:33pm
my guess is, you forgot something important
Copy all of the following text.Then, in Max, select New From Clipboard.
----------begin_max5_patcher----------
659.3oc2W0riaBCD9L4ovKW5kzHrASfdnR8XeFpVUY.uDWA1Qfi1ztZe2K1F
xuDGHkMsauXBiGF+MeyOdxKybbSDao0tfOA9Fvw4kYNNZQJANsu63VR1lVPp
0p4lJJKobo6bydR5VoV9m6j7TUdhwfdKhgKCCVNu4WdsKvEdfGa0bMQlthwy
+dEMUZ9DTXfRqHjV2X0Jx6fOgkoOLQxO9HLX2IJ3RNojp25KULRQ2N7MkLdA
UpgN7.HmJJDUCCkM1PrQ1YDuCNyZ1uzmIrAsJouNalZY9+FLoOVoUP7.XR++
SYR4JhDvpArx0hJIYuFELNMUrgqUCMEzci9JsvP0pII1One598ddKm9biabN
YCR.ItVRHwZHZV8CrlPdiLzwtbWbcDb1orSqXiQk+bM0XF2DBO2cd6SviSGI
hrPf9dZ7FYHPzB7kIv3QRfndIP3HYElpd5VHiRZcMImdFaHDqqe.7UvyjZ9G
jfBAISw3zrGrPSvnHcXMTWJBw95GQ8STg+UHpIMkImHo.D.d8LGHReM.1ZsG
dRXDzXYj42JqnQhMe+v6AQ3t0da6.60C8rFy6K3tqwi4ZIk8cuAWKYiTJ3W2
2hV1EPszR0aDcNgV66Mok35h6CqrA4Bg05aerY3vPSNc.zV8cz6n5aiYr44s
iwghtdt7xQDt8ln70KzfpK3d8YCf5D4PqIxnIY1.3sbg+QQUM1zCRdxeeR6d
J4GyT0hMUoclqcHGvdOLiVKYbhj0TvuWmllw.3NcVwxxn7iiXCdzlRV1ZQyM
zsn8BYniA7vq.93ibvyA+zhHz.nS3cEQwCL.e+Pj5Rf+3btoER3Afnv6JIgG
Ppcz8MrMjVEmDaeqwTz.fzx6JhBeiQTyKuN62XVXX8G
-----------end_max5_patcher-----------
|
|
|
Jun 29, 2010 at 6:03pm
>my guess is, you forgot something important
It doesn’t seem to work.
Does it works for you?
m
|
|
|
Jun 29, 2010 at 9:40pm
my guess was a complete misunderstanding of the problem
|
|
|
Jun 29, 2010 at 9:46pm
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.
|
|
|
Jun 30, 2010 at 3:55am
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?
|
