On Tue, Nov 17, 2015 at 4:15 AM, Roman Haefeli <[email protected]> wrote:
> Hey, thanks for addressing the issue. > > On Mon, 2015-11-16 at 15:25 -0500, Martin Peach wrote: > > So I updated packOSC in svn to detect reentrancy and post a message. > > The message says: > error: packOSC: Use bundle to send multiple messages > > I find this message a bit misleading as I'm not at all trying to create > a bundle. I'm simply creating an OSC packet that in returns triggers > another OSC packet to be generated. I expect [packOSC] to treat them > absolutely separately. > > What should it say then? "packOSC is being asked to process another message before it is finished with the current one"? > > It seems too complicated to allow it. > ...but I'll keep thinking about it. There may be a way. > > I see. It's not complicated at all on a patch level to make [packOSC] > allow reentrancy. See attached patch. I can live easily without it being > fixed in [packOSC]. > > And this is the _expected_ output from my previous patch (and it > actually _is_ the output of the currently attached patch with the > work-around): > > FIRST: /i/am/reentrant 64 > SECOND: now > > Here's another patch that does the same thing by using two [packOSC]s. Martin
#N canvas 710 148 450 269 10; #X declare -stdpath osc -stdpath mrpeach; #X obj 17 98 packOSC; #X obj 17 120 unpackOSC; #X msg 17 16 /trigger/osc/message now; #X msg 49 193 /i/am/reentrant 64; #X obj 17 142 routeOSC /trigger/osc/message; #X obj 17 164 t a b; #X obj 17 230 print SECOND; #X obj 217 230 print FIRST; #X obj 208 16 declare -stdpath osc -stdpath mrpeach; #X obj 75 98 packOSC; #X connect 0 0 1 0; #X connect 1 0 4 0; #X connect 2 0 0 0; #X connect 3 0 9 0; #X connect 4 0 5 0; #X connect 4 1 7 0; #X connect 5 0 6 0; #X connect 5 1 3 0; #X connect 9 0 1 0;
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
