On 11.12.2023 16:10, IOhannes m zmoelnig wrote:
the simplest check would just be whether the filename of the
containing patch ends with "-help.pd"
I actually had this thought, but rejected it for being too gross :-D
Also, it does not really work because [aoo_send~ 2] and [aoo_send~ -m 2]
hav
On 12/11/23 16:04, Christof Ressi wrote:
Interesting. The big disadvantage is that the roles are reversed: what
should be a subpatch is now the root window, so when the user tries to
close it, it closes the whole help patch... So I guess I'd rather prefer
my current solution.
totally. i was
On 12/11/23 15:29, Christof Ressi wrote:
Ok, I have a come up with the following solution: I moved the
multichannel section into a dedicated patch and open it with [;pd
open 1( when the user clicks a bang button in the main
help patch. It's not perfect, but kind of works for my purposes.
so
On 12/11/23 15:29, Christof Ressi wrote:
Ok, I have a come up with the following solution: I moved the
multichannel section into a dedicated patch and open it with [;pd open
1( when the user clicks a bang button in the main help
patch. It's not perfect, but kind of works for my purposes.
so
Ok, I have a come up with the following solution: I moved the
multichannel section into a dedicated patch and open it with [;pd open
1( when the user clicks a bang button in the main help
patch. It's not perfect, but kind of works for my purposes.
I am still wondering if anyone has run into
Hi,
I have a library with /optional /multi-channel support. If you try to
create the object with the "-m" flag and Pd does not have multi-channel
support, it would print an error message. This works all fine, but
there's a tricky problem with the help patches. Of course, I want to
document th
