Exactly. I'll often use one (or its signal equivalent [*~ 1]) as an anchor point or temprorary placeholder for something with a large in/out degree but undecided function. Like a way to 'hang on' to a bunch of connections in working memory. Hubs often represent points that will either break out (become outlets to a parent) or become subpatches. Having an object already there means its name can be replaced by [outlet] or [pd newfunction] without remaking those cords.
Since they look rather ugly and sick out like a sore thumb, they are easily cleaned up at the end. I've often wondered is there any penalty overhead if you leave a few lying around? I assume its negligable. On Tue, 13 Sep 2011 15:39:15 -0400 (EDT) Mathieu Bouchard <ma...@artengine.ca> wrote: > On Mon, 12 Sep 2011, Jonathan Wilkes wrote: > > > Yes, I forgot about the hub. There's that, too. But if you have a [t > > a] with one wire in and one wire out then chances are you ought to have > > used a segmented wire. But those aren't available, so you use [t a], > > and in these cases I give it a minus one. > > Not necessarily... when I have a [t a] with a single wire on each side, > chances are that it's a past hub or a future hub or both. > > _______________________________________________________________________ > | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC -- Andy Farnell <padawa...@obiwannabe.co.uk> _______________________________________________ Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list