Nov 30, 2012 at 11:41pm
click the “b” message box. Since there is @triggers 1, the stack should not overflow!
– Pasted Max Patch, click to expand. –
Copy all of the following text.Then, in Max, select New From Clipboard.
OSX 10.6.7, Max6.0.8
(dev note: this seems to me related to the fact that proxy_getinlet() returns 1 instead of 0 in this recursive context)
Dec 2, 2012 at 11:00am
don’t know if this is relevant, but a deferlow between the output of the combine and the trigger stops the recursion
Dec 2, 2012 at 12:39pm
@andrea proxy based object doesn’t support recursion. When you enter the combine object from the right inlet, you are in the outlet call of message “b”, when you enter the combine object it’s from inlet 1 and everything which is happening after is still coming from the original message so, for combine you’re still using the inlet 1, which triggers.
@Terrry: that’s a good way to avoid the recursion indeed.
Dec 3, 2012 at 6:14pm
Salut Manu ;)
Yes, that’s what I feared… but recursion actually works with proxy-based objects, as long as the main inlet doesn’t come into play… no hope to have that working for the main inlet as well in some future release? And no other way to tell if a message is coming from the main inlet, instead of a proxy? (maybe this should be moved to the Dev forum though…)
You must be logged in to reply to this topic.