[PD] inlet names (bad?) practice?

Alexandre Torres Porres porres at gmail.com
Tue Mar 2 19:56:02 CET 2021


Thanks for the pointers, I don't see this implemented in Extended (42/43)
or in Purr Data by extension. By readng the discussion, the patch was never
included in the distribution, right?

So it was more like a plan than a reality?

Em ter., 2 de mar. de 2021 às 15:20, Claude Heiland-Allen <
claude at mathr.co.uk> escreveu:

> On 02/03/2021 17:45, Jonathan Wilkes via Pd-list wrote:
> > > On Tuesday, March 2, 2021, 11:10:36 AM EST, Alexandre Torres Porres
> > <porres at gmail.com> wrote:
> >
> > > Hi, I was asking people on facebook where did they get the idea of
> > putting names in inlets/outlets, like: [inlet
> > this-inlet-controls-frequency].
> >
> > Not sure. But A_DEFSYM and A_DEFFLOAT are implemented in a way that
> > allows an arbitrary number of extra float/symbol arguments, so it
> > could be `[inlet this inlet controls frequency]`. Or following the
> > `[get]` and `[set]` pattern-- `[inlet - this inlet controls
> > frequency]` to skip over the first arg that is currently used for
> > up/downsampling.
> >
> > Someone asked on the Purr Data list about this. It would be easy to
> > implement, but it doesn't cover the case of setting a description for
> > the object itself. Plus I'd much rather just leverage the
> > documentation index in the GUI to look up tooltip data.
> >
> > -Jonathan
> https://download.puredata.info/dev/InletDescriptions
>
>
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> https://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20210302/a59c60fe/attachment-0001.htm>


More information about the Pd-list mailing list