[PD] Behaviour of nested GoP abstractions

IOhannes m zmoelnig zmoelnig at iem.at
Wed Sep 14 18:08:04 CEST 2005

Frank Barknecht wrote:
> You can also make a wrapper abstraction: let [gop-abs] be a GOP
> abstracion. A wrapper would be [gop-abs-nogui] which has GOP switched
> *off* and just has an instance of [gop-abs] with connected in/outlets
> inside. 

another solution would be to just put all the guts into [abs] and 
[gop-abs] is just a wrapper around [abs].
so if you are changing the implementation details of [abs] you would 
just have to save that one, and [gop-abs] would be updated too.
if you are changing the interface, you would of course have to change 
[gop-abs] too.

a third solution might be, to turn gop on/off depending on creation 
arguments. there is some message you can send to an abstraction that 
makes it gop or not (but i am not sure how stable this is).
like [abs] would be non-gop, but [abs gop] would make it gop. (or the 
other way round, of course)


More information about the Pd-list mailing list