<html><head></head><body><div style="font-family: Verdana;font-size: 12.0px;"><div>I was wondering about that too! After a quick search in the mailarchives I've found this discussion from 2008: http://lists.puredata.info/pipermail/pd-list/2008-06/062895.html</div>
<div> </div>
<div><span style="line-height: 1.6em;">@IOhannes: What's the state now? How difficult would it be to make an [inlet~] external which, for example, passes signals to a left outlet and all messages (also floats!) to a right outlet. Or which passes everything it receives and then you could use [route~] from zexy to separate signals from messages?</span></div>
<div> </div>
<div> </div>
<div>
<div style="margin: 10.0px 5.0px 5.0px 10.0px;padding: 10.0px 0 10.0px 10.0px;border-left: 2.0px solid rgb(195,217,229);">
<div style="margin: 0 0 10.0px 0;"><b>Gesendet:</b> Freitag, 18. September 2015 um 12:49 Uhr<br/>
<b>Von:</b> "Liam Goodacre" <liamg_uw@hotmail.com><br/>
<b>An:</b> "pd-list@lists.iem.at" <pd-list@lists.iem.at><br/>
<b>Betreff:</b> [PD] getting [inlet~] to accept data</div>
<div>
<div class="hmmessage">
<div>Many objects (ie. [osc~]) have a sort of a hybrid inlet which accepts both signal and data input. However, the [inlet~] object seems to reject data. If I wanted to build an abstraction with an [inlet~] that accepts both signal and data, is there any other way?</div>
_______________________________________________ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a></div>
</div>
</div>
</div></div></body></html>