| From | Sent On | Attachments |
|---|---|---|
| Mathieu Bouchard | Jun 29, 2004 10:58 am | |
| Frank Barknecht | Jun 29, 2004 11:22 am | |
| raymond | Jun 29, 2004 12:56 pm | |
| Lee Azzarello | Jun 29, 2004 2:28 pm | |
| Frank Barknecht | Jun 29, 2004 3:34 pm | |
| raymond | Jun 29, 2004 5:55 pm | |
| Eric Skogen | Jun 29, 2004 6:23 pm | |
| zmoe...@iem.at | Jun 30, 2004 12:12 am | |
| Mathieu Bouchard | Jun 30, 2004 9:56 pm |
| Subject: | Re: [PD] gate | |
|---|---|---|
| From: | zmoe...@iem.at (zmoe...@iem.at) | |
| Date: | Jun 30, 2004 12:12:57 am | |
| List: | at.iem.pd-list | |
Zitiere Mathieu Bouchard <mat...@sympatico.ca>:
[demux] that was in jMax, and actually it was called [demux] in GridFlow before, but there's a conflict with the alias [demux] of the [demultiplex] class in Zexy, which takes args more like [unpack] than like [gate].
oh, another name-clash in one of my libs... (probably the IEM should get the nameclashing award), i hope it has been there before the GridFlow version.
as for the "weird" [unpack]-behaviour, i chose to do so because of readability: as long as objects are not resizable, a [demux] with 20 outlets is rather hard to read if there is not some mechanism to make it wider than 8 characters.
but i really could make it compatible with a single-argument [demux] (as i suppose, nobody has a demulitplexer with just one outlet...)
are there any functional differences (as i always thought, that zexy's [demultiplex] does exactly what a demultiplexer should do: demultiplex a data-stream to one of many outputs)
mfg.a.dsr IOhannes





