[PD] use case of 'isvisible' in [pdcontrol]?

Alexandre Torres Porres porres at gmail.com
Thu Dec 5 09:51:39 CET 2019

Em qua., 4 de dez. de 2019 às 22:36, Miller Puckette <msp at ucsd.edu>

> it's bad to copy information around and better to always have access
> to one centralized variable that you can check when needed.

Ok, I think I get it now. Say you got controllers sending info and you want
them to go through just when the patch is visible, then when the data comes
in you check wether the patch is visible or not so you can let it through.
Kinda like that, right?

I do that for the patch window that is in the 'top level' - cyclone has
[active] for that but it sends you the status when it changes. Liam asked
me for an object that would also give you the status of a parent patch.
Never used that, but I guess I can see why you'd need it for abstractions.

Likewise, maybe you want something to happen only if the parent patch
containing the abstraction is visible - seems to be useful if your
abstraction generates interactive graphs, for instance, and there you have
it, a use case. I do have an abstraction that generates spectrographs for
display in ELSE and then I could turn its DSP off (with [switch~]) when
it's not visible and needed. So it seems I found a use case after all, I'll
try this out.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20191205/f066d563/attachment-0001.html>

More information about the Pd-list mailing list