monohusche

I am working with a two level bpatcher structure, the main patcher contains 8 bpatchers referring to the same abstraction X (not embedded).

The abstraction X contains multiple other bpatchers Y,Z,... (not embedded). The inspector of the 8 bpatchers on level 1 contains a unique identifier as an argument (ch1, ch2, ch3,..) which is used within X and also within Y and Z (by putting #1 into the respective inspectors).

For some reason, the arguments (ch1, ch2,ch3) don't get propagated correctly, so I am wondering what the best strategy for those kind of cases is.

The patcher in question is pretty massive, therefore I hope, my long winded explanation isn't too confusing.

I am working with a two level bpatcher structure, the main patcher contains 8 bpatchers referring to the same abstraction X (not embedded). 

nested-bpatcher-arguments-problem

On 25 janv. 09, at 19:41, Nick Laqua wrote:

> I am working with a two level bpatcher structure, the main patcher 

> contains 8 bpatchers referring to the same abstraction X (not 

> The abstraction X contains multiple other bpatchers Y,Z,... (not 

> embedded). The inspector of the 8 bpatchers on level 1 contains a 

> unique identifier as an argument (ch1, ch2, ch3,..) which is used 

> within X and also within Y and Z (by putting #1 into the respective 

> For some reason, the arguments (ch1, ch2,ch3) don't get propagated 

> correctly, so I am wondering what the best strategy for those kind 

> The patcher in question is pretty massive, therefore I hope, my long 

> winded explanation isn't too confusing.

I can't reproduce. Could you provide a patch?

> Hi there,
>
> I am working with a two level bpatcher structure, the main patcher  
> contains 8 bpatchers referring to the same abstraction X (not  
> embedded).
>
> The abstraction X contains multiple other bpatchers Y,Z,... (not  
> embedded). The inspector of the 8 bpatchers on level 1 contains a  
> unique identifier as an argument (ch1, ch2, ch3,..) which is used  
> within X and also within Y and Z (by putting #1 into the respective  
> inspectors).
>
> For some reason, the arguments (ch1, ch2,ch3) don't get propagated  
> correctly, so I am wondering what the best strategy for those kind  
> of cases is.
>
> The patcher in question is pretty massive, therefore I hope, my long  
> winded explanation isn't too confusing.

I went back to working with two layers of objects, solved my problem and makes it easier overall.

might have a look again when there is more time, thx anyway.

nested bpatcher arguments problem