Ability for computer probe to read/write individual signal bus cables

[vety010]

Speaks for itself. Would be nice if signalGetIn() and signalSetOut() had an additional optional argument specifying the channel of a signal bus cable to read from/write to.

[jrddunbr]

The reason we did it that way is that due to the limitations of the implementation, we can only get one call per tick out of OC. So if you wanted to read all 16 signals individually, that would take 16 ticks or just under a second. Reading a sigbus on all 5 sides would result in something like 4 seconds of read time.

Not saying this isn't a good idea, I'll keep the issue open and consider it at some point soon.

[vety010]

Another variation of the idea would be to read 16 values at once and pass them as a table. That will be exactly one call as far as OC should be concerned and I assume there are no limitations on reading within ELN

[jrddunbr]

Huh. Does it not do that already? That should certainly be doable.

[vety010]

Well, the probe interface lists a bunch of functions, the only one being able to read input values being <ElnProbe>.signalGetIn. Calling it with a signal bus connected to the side (and with the side being set as an in) does not return a vararg nor a table. It only returns the value on the black channel of it.