I recently implemented a variant of delread~ that can have it's delwrite~ set. Basically in the "set" messageI just did most of the things normally done in the dsp method. Instead of sending the pointer to the delwritectl to the performmethod using dsp_add, instead I send a pointer to a pointer to the delwritectl that is stored in the object dataspace.That way, when a different delwrite is set I just have to store the pointer in the object dataspace and dereference it correctlyin the perform method:you can see it in the .c files in this commithttps://github.com/sebshader/shadylib/commit/8bdf985aacb3979e776ad4e2487c451fadb9864a
-seb -----Original Message----- From: Alexandre Torres Porres <[email protected]> To: Christof Ressi <[email protected]> Cc: Pd-List <[email protected]> Sent: Mon, Mar 1, 2021 5:08 pm Subject: Re: [PD] how to force the DSP call? / set delread~ delay name Em seg., 1 de mar. de 2021 às 20:40, Alexandre Torres Porres <[email protected]> escreveu: I can also try a PR I give up already, waiting for you :) Em seg., 1 de mar. de 2021 às 21:02, Christof Ressi <[email protected]> escreveu: Pd objects are (unfortunately) not notified on connection changes and I can't think of a sane way to work around this. The real solution would be to add an API for object state change notifications. In the meantime, I would say: forget about it. forgotten, but: https://github.com/pure-data/pure-data/issues/1275 while we're at it, any reason why not to have a "set" method for [send~] and [catch~]? Seems inconsistent_______________________________________________ [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
