[PD] knowing if there's anything connected to an [inlet~] in a subpatch or abstraction

[Alexandre Torres Porres]

I'm actually interested in knowing whether there's a signal connected to
the inlet of an abstraction.

I need it so I can automatically switch between the argument loaded in the
abstraction and whatever is going to that inlet from a signal connection.

But I guess it is kinda impossible to it in a patch... so it may be only
possible as an external...

"*all of Pd's binops (e.g. [+~]) take an optional argument, and the type*


*of the second inlet depends on the existance of this argument (ifthere is
no argument, you get a signal inlet, if there is an argument**you get a
message inlet).*"

but is it possible to write an external with a different behaviour like I
need?

"*finally: i haven't looked at your abstraction, but i guess the problem*


*you are facing is to distinguish between no argument and the default"0"
argument. it's possible to do this as a vanilla abstraction. check**the
list archives for examples.*"

that seems like a separate issue, one that I actually care about, so I'll
maybe check it.

cheers


2015-02-25 5:25 GMT-03:00 IOhannes m zmoelnig <zmoelnig at iem.at>:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 2015-02-24 18:52, Alexandre Torres Porres wrote:
> > "I think that even in the case of an external, it's difficult to
> > know whether there's a signal connected to a signal inlet, or not
> > (...) I think Eric Lyon's externals do what you want"
> >
> > I guess it can be tricky, but not impossible.
>
> i think you are asking the wrong question here: you are not at all
> interested in whether an object has a signal connected or not, but
> only whether you can provide a "default signal".
>
> while the former might be tricky, the latter might not be.
>
>
> otoh, i'm not entirely sure whether you "should" really want what you
> are asking for.
> in a "max compat" sense it might make sense, but it's not very Pd'ish:
> all of Pd's binops (e.g. [+~]) take an optional argument, and the type
> of the second inlet depends on the existance of this argument (if
> there is no argument, you get a signal inlet, if there is an argument
> you get a message inlet).
>
> finally: i haven't looked at your abstraction, but i guess the problem
> you are facing is to distinguish between no argument and the default
> "0" argument. it's possible to do this as a vanilla abstraction. check
> the list archives for examples.
>
>
> fgmasdr
> IOhannes
>
> PS: as far as zexy is concerned, i will keep it as Pdish as possible.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQIcBAEBCAAGBQJU7YcEAAoJELZQGcR/ejb4ZoYP/Ao0qYb0voK1j8BWVFoBrCgy
> tSbO3yYcO/WzFQBEc6ZBWf5CooRjWGnI/3xO0ZUXyfNlv073O49ra4Oe1NoPRlEQ
> P37Z8jwACO1cBel8lBVlZ80l3WsKGKRf7UynF3sVI5HJaIjOK5I5ssb6FNWl2cM3
> FFluN226XXqCjtdYMfeRkIalEpH9BVIzflL+H3kZ9oBUA9ZHUVQ1ifpIOsxrn6df
> Z/K1uwmNKYauwUwqvpm2ARUbAyINoD1WiagITE3GOVcSddsO9OnJYiZVnOH8XulU
> z9AfAwFWjQPI8fTsvORWBDBhDUce3WFOuZ4ZCyqzVw9RQlmMq1Q4HYGYoPBinOM1
> vYR92sqEOHrZhN8nal6rTsYCmy5BLJeprU7mWrxr+GrA5CLv2fvBbL3E6uTD9Xz9
> Q5+lR+4FLexxVDDIAI7fnM+RADYLWTQuCytENPiUDzcfmv/g+KWGIXH2+yvu4/UR
> j+1wGUyAfHYmL59GEpla0ZmQonkN/1hyq3yBYlo8Oz0+D038ixjRu8LpB4pTHDFm
> KCiuOo35vkUfyZz2gCU8/5JE9aXr/fjaYt3VLgxpbCRjgRoW2Y0wtJosNl/4DCeK
> 61RKMaZPYEjY19K8k3Pi0X/xSdep7dAClldT+KF5FkbpBjGdUG9rJcEMFtteYPKz
> g7Slg3igjpG4dXBG5wFK
> =y1hh
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management ->
> http://lists.puredata.info/listinfo/pd-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20150225/84275141/attachment.html>