Cool, but what did you have in mind? Like what use cases to include this? I thought I'd need it for a patch, and then it turned out I didn't need it... not even worth mentioning. Anyway, at that moment, I also thought it could be useful to have it query for the visibility of a parent patch and stuff, so I went ahead and opened the request https://github.com/pure-data/pure-data/issues/803
I was actually gonna go ahead and propose a PR for it, but like I said, it turns out I didn't need it, and then I'm now wondering why would someone need this and if in fact it's a good and desirable idea for giving it an argument. If people think it's cool and that they'd need something like this, I can go ahead and make a PR, otherwise, I don't know, but probably I'll close it. cheers Em qua., 4 de dez. de 2019 às 22:36, Miller Puckette <[email protected]> escreveu: > My opinion which you should take with a grain of salt if not a whiff of > HCN, > is that it's bad to copy information around and better to always have > access > to one centralized variable that you can check when needed. Anytine data > is > duplicated there's a worry that different copies will get out of sync. > > cheers > M > > On Wed, Dec 04, 2019 at 10:22:12PM -0300, Alexandre Torres Porres wrote: > > Hi, I'm curious about the use cases of the 'isvisible' message in > > [pdcontrol], and I also wonder how useful is it to query for the > visibility > > state instead of just getting it when it changes. > > > > cheers > > > _______________________________________________ > > [email protected] mailing list > > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > >
_______________________________________________ [email protected] mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
