It seems I can't recall an ubumenu state (put in subpatcher) from a [pattr @bindto] when this ubu is set in pattrmode 1. works fine in pattr mode 0

ubumenu-pattrmode-1-inexpected-behavior

pattrmode 1 is content-based, not index-based. You're sending the index of the item you want (left outlet of ubumenu), rather than the name of the item in the menu (middle outlet of ubumenu).

No, sorry, not so simple, look at the patch below.

For me [pattr] object doesn't want ubumenu to be in pattrmode 1 for showing its content as symbol when @bindto subpatcher ?

But I'm still expecting for a max4 to max5 translator (even if it seems difficult).

For me [pattr] object doesn't want ubumenu to be in pattrmode 1 for showing its content as symbol when @bindto subpatcher ? 

... Perhaps it is time for to run Max5.
But I'm still expecting for a max4 to max5 translator (even if it seems difficult).

On Jun 3, 2008, at 9:20 AM, Derrick Giscloux wrote:

> But I'm still expecting for a max4 to max5 translator (even if it 

Max 5 already does a pretty good job of importing Max 4 patchers.

Perhaps you mean a Max 5 to Max 4 translator? (which I would wager 

On Jun 3, 2008, at 9:20 AM, Derrick Giscloux wrote:
> But I'm still expecting for a max4 to max5 translator (even if it  
> seems difficult).

Perhaps you mean a Max 5 to Max 4 translator? (which I would wager  
never gets created)

Chris Muir
cbm@well.com	
http://www.xfade.com

There appears to be a minor difference in the two modes: in pattrmode 1, you need to explicitly send the ubumenu's toggle state, whereas you can leave it unspecified in pattrmode 0. Here's a workaround.

ubumenu pattrmode 1: inexpected behavior