LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Norbert_B

Access Channel Wire by name

Status: Declined

Declined for reasons listed by AristosQueue in the discussion thread

Starting with channel wires makes me wonder why it requires a wire (besides by the technologies name that is) at all.

I would prefer it to simply use "terminals". Selection of the used channel wire by the terminal is done by passing a name similar to named queues. The channel wire itself is obsolete by that which would also conclude the discussion about "channel wire direction indication".

Usage of 'channel wire terminals' will be similar to shared variable nodes.

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
6 Comments
Intaris
Proven Zealot

Visualisation of communication channels is a big point.

 

One typical usage of the channels is inter-loop communication on the same BD.  Removing the wire would make the communication as clear as when using locals, which is not very good at all.

Norbert_B
Proven Zealot

While i concur with your point, having wires is a huge minus for bigger applications.

Having to pass wires to subVIs limits usage similar as it does for user events or DVRs. Flexible architectures launching an arbitrary number of equal processes have a hard time making effective use of "wired technologies".

 

I am not stating the getting rid of the wire makes it that much easier to work with. However, it gets more in line with already known structures and usage will get more flexible (when following the rules).

Also see that idea which will be possible when naming channel wires.

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
crossrulz
Knight of NI

In the end, the Channel Wire is just a queue (overly simplified here).  So if you do not like the wire, don't use it.  Just use the queue like you do now.  I do not see a reason to change Channels into something that it was trying to avoid/"fix" from the beginning.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
donkdonk
Member

As pointed out by Intaris, it's all about visualization. It's in fact the detailed implementation of my rough idea here (and others have written about asynchronous wires for a long time). If you don't want wires, check out the free vi register toolkit by "GPower". It covers a lot of 'intra-proces communication'. I find them very versatile and easy to use. Note that I am not in any way (financially) connected to this company ;-). 

AristosQueue (NI)
NI Employee (retired)

This request defeats the entire purpose of the feature. If you do not wish to use channels, use an existing communications mechanism. We will not be making this change.

Darren
Proven Zealot
Status changed to: Declined

Declined for reasons listed by AristosQueue in the discussion thread