I'm in the middle of a mid-sized project using Pure Data and I just wanted to say thank you to all involved with writing the new undo system and integrating it into Pd vanilla.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
Everytime i'm feeling stressed, sad or anxious i think about the new features in the 0.49 release and the pain goes away.
Cheers, Henri.
De: Pd-list pd-list-bounces@lists.iem.at em nome de Dan Wilcox danomatika@gmail.com Enviado: sexta-feira, 9 de novembro de 2018 13:40 Para: Pd-List Assunto: [PD] Thank you for undo!
I'm in the middle of a mid-sized project using Pure Data and I just wanted to say thank you to all involved with writing the new undo system and integrating it into Pd vanilla.
Dan Wilcox @danomatikahttp://twitter.com/danomatika danomatika.comhttp://danomatika.com robotcowboy.comhttp://robotcowboy.com
Hi folks, I wrote an external based on [namecanvas], but it can also name the parent patch. My use case was that I wanted to keep it in a subpatch to make my code cleaner, but that didn't feel like an excuse for a new external. Nonetheless, I thought that there could be probably nice if you could use this inside an abstraction and name a parent patch, who knows? The thing is that if this was needed already, it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).
So I asked about it on the facebook group and I got a feedback from Henri, saying this would be quite useful as a workaround for this issue Pd has, where you need to send the parent patch a |map 0, map 1< message so it redraws - here's a discussion about it https://forum.pdpatchrepo.info/topic/9454/full-support-for-gop-dynamic-patch...
Now I'm more comfortable in providing this external, but it is also the case where this could be thought as a Pd bug and eventually taken care of.
So, in order to learn more from those who do lots of dynamic patching, I'm also asking here on this list if you think this could be actually useful for other use cases.
ps. as long as we're at it, why is [namecanvas] considered "not safe" and "probably should go away, but there's no replacement yet"?
cheers
Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres < porres@gmail.com> escreveu:
it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).
yeah, I should have looked more carefully, at first glance I missed it completely, but I dug in more deeply, object one by one, and found out that iemguts has a [sendcanvas] object which also does that :)
so yeah, apparently this is a useful feature for one reason or another...
For the record, I guess I should have said I'm deciding to forget about adding such an object to my library, since [sendcanvas] already takes care of this (so we don't need yet another one) and also cause I can deal with this inside the abstractions of my library with vanilla objects anyway...
sorry for the noise
Em sáb, 10 de nov de 2018 às 19:56, Alexandre Torres Porres < porres@gmail.com> escreveu:
Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres < porres@gmail.com> escreveu:
it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).
yeah, I should have looked more carefully, at first glance I missed it completely, but I dug in more deeply, object one by one, and found out that iemguts has a [sendcanvas] object which also does that :)
so yeah, apparently this is a useful feature for one reason or another...
Since you've touched the of sending |map 0, map 1( from an abstraction to it's parent¹ allow me to ask this in the dev list:
The only way i know only with vanilla objects is to use a [namecanvas] on the parent and pass it's name as an argument or through an inlet. Do you (or anyone reading this) happen to know a more elegant way? Perhaps something new recently introduced under the hoods in the latest PD releases, idk
Cheers, Henri.
¹ https://forum.pdpatchrepo.info/topic/9454/full-support-for-gop-dynamic-patch... (putting it here since it wasn't present in the replies below)
De: Pd-list pd-list-bounces@lists.iem.at em nome de Alexandre Torres Porres porres@gmail.com Enviado: sábado, 10 de novembro de 2018 20:27 Para: Pd-List Assunto: Re: [PD] naming a parent patch: is this external useful?
For the record, I guess I should have said I'm deciding to forget about adding such an object to my library, since [sendcanvas] already takes care of this (so we don't need yet another one) and also cause I can deal with this inside the abstractions of my library with vanilla objects anyway...
sorry for the noise
Em sáb, 10 de nov de 2018 às 19:56, Alexandre Torres Porres <porres@gmail.commailto:porres@gmail.com> escreveu: Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres <porres@gmail.commailto:porres@gmail.com> escreveu: it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).
yeah, I should have looked more carefully, at first glance I missed it completely, but I dug in more deeply, object one by one, and found out that iemguts has a [sendcanvas] object which also does that :)
so yeah, apparently this is a useful feature for one reason or another...
Em sáb, 10 de nov de 2018 às 22:56, Henri Augusto Bisognini < msndohenri@hotmail.com> escreveu:
The only way i know *only with vanilla objects* is to use a [namecanvas] on the parent and pass it's name as an argument or through an inlet. Do you (or anyone reading this) happen to know a more elegant way?
I'm convinced this definitely needs an external, or a fix for not needing to send |map 0, map1< in the first place. As discussed in that thread, the problem is that using the '*donecanvasdialog*' to change GOP parameters doesn't work well because things aren't redrawn.
Perhaps something new recently introduced under the hoods in the latest PD releases, idk
so, yeah, perhaps we can open an issue/request to include something that expands and improves dynamic patching, such as a new message method that makes using '*donecanvasdialog*' obsolete.
Cheers, Henri.
¹ https://forum.pdpatchrepo.info/topic/9454/full-support-for-gop-dynamic-patch... (putting it here since it wasn't present in the replies below)
*De:* Pd-list pd-list-bounces@lists.iem.at em nome de Alexandre Torres Porres porres@gmail.com *Enviado:* sábado, 10 de novembro de 2018 20:27 *Para:* Pd-List *Assunto:* Re: [PD] naming a parent patch: is this external useful?
For the record, I guess I should have said I'm deciding to forget about adding such an object to my library, since [sendcanvas] already takes care of this (so we don't need yet another one) and also cause I can deal with this inside the abstractions of my library with vanilla objects anyway...
sorry for the noise
Em sáb, 10 de nov de 2018 às 19:56, Alexandre Torres Porres < porres@gmail.com> escreveu:
Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres < porres@gmail.com> escreveu:
it would probably exist somewhere, specially in [iemguts] of all places, but I couldn't find this functionality there (or I just missed it completely).
yeah, I should have looked more carefully, at first glance I missed it completely, but I dug in more deeply, object one by one, and found out that iemguts has a [sendcanvas] object which also does that :)
so yeah, apparently this is a useful feature for one reason or another...
-
Alexandre Torres Porres -
Dan Wilcox -
Henri Augusto Bisognini