On Mon, 17 Dec 2007, Derek Holzer wrote:
Still, it is an inherent part of PD that you keep messages and audio
separate. Thus the different graphical look of the patch cables, and the
fact that it will not let you connect an audio cable to a non-audio
object. There must be some reason for this, and speed of the objects is
what I thought it was.
It's just that a signal inlet doesn't know what to do with a non-signal
input, and a non-signal inlet doesn't know what to do with a signal input.
There's not much reason why the look of câbles wouldn't be different
depending on whether they carry floats vs symbols vs whatever else. The
GUI could also try to assist you more by investigating more about which
connections don't make sense. There is a hint that Miller had such a thing
in mind at one point and ended up not implementing it. You can see it in
how outlet_new is defined and used: most classes declare a type for each
of their outlets. Currently this is only used for signal vs non-signal,
even though many classes define outlets with typenames like "float",
"symbol", "pointer", "anything", ...
_ _ __ ___ _____ ________ _____________ _____________________ ...
| Mathieu Bouchard - tél:+1.514.383.3801, Montréal QC Canada
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
