Re: [PD] naming a parent patch: is this external useful?

2018-11-10 Thread Alexandre Torres Porres
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...

Re: [PD] naming a parent patch: is this external useful?

2018-11-10 Thread Alexandre Torres Porres
Em sáb, 10 de nov de 2018 às 18:13, Alexandre Torres Porres < por...@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

[PD] naming a parent patch: is this external useful?

2018-11-10 Thread Alexandre Torres Porres
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