Chris

anoying-bug-with-maxpatcher-getallboxes

> MaxBox[] boxes = getParentPatcher().getAllBoxes();

Ooh ... as a wild guess, I'd say that getParentPatcher().getAllBoxes 

() is not safe to call in your constructor, since the patcher is 

still being built as your MXJ object is being created and its 

nick rothwell -- composition, systems, performance -- 

> Contructor of mxj object contains:
> ----------------------------------
> MaxBox[] boxes = getParentPatcher().getAllBoxes();

Ooh ... as a wild guess, I'd say that getParentPatcher().getAllBoxes 
() is not safe to call in your constructor, since the patcher is  
still being built as your MXJ object is being created and its  
constructor called.

   nick rothwell -- composition, systems, performance -- http:// 
www.cassiel.com


>> MaxBox[] boxes = getParentPatcher().getAllBoxes();

> Ooh ... as a wild guess, I'd say that getParentPatcher().getAllBoxes() 

> is not safe to call in your constructor, since the patcher is still 

> being built as your MXJ object is being created and its constructor called.

yes yes yes... this seems a very good reason for my problem...

I'll move the code to loadbang to see what's happening.

>> Contructor of mxj object contains:
>> ----------------------------------
>> MaxBox[] boxes = getParentPatcher().getAllBoxes();
>
> Ooh ... as a wild guess, I'd say that getParentPatcher().getAllBoxes() 
> is not safe to call in your constructor, since the patcher is still 
> being built as your MXJ object is being created and its constructor called.

That's working fine now... thanks for your help

Anoying bug with MaxPatcher.getAllBoxes