How to know if a wire is connected to a control (in the case of subVI)?

[Ben]

Adding to my previous...

I am an old man that taught himself to program in machine languages* and have climbed through software gradually moving to more and more abstract versions. Over time I have subjected myself to many changes to the way I think about code. It is taking me some time but I am getting close to "seeing" LVOOP in the context of the And-Gates and OR-Gates that comprise my mental image of the code I develop. That statement may not make much sense to those out there that started out programming using an editor to produce files that can be compiled and linked. Just think of it like "Ben has has an extra Platform Abstraction Layer that has to be adapted to the new developement environment.".

But thank you!

I'll keep trying.

Ben

* In 1988 I converted from "012737" = Move the data in the location following this instruction to the loaction pointed to by by the location that follows that

to

mov R7, @R7

PDP-11 instruction set equivelant of a wire in LV.

Message Edited by Ben on 05-05-2009 08:29 AM

Message Edited by Ben on 05-05-2009 08:30 AM

[GerdW · Accepted solution]

Hi Rob,

"OR

- Do I test control defaults values and determine if a wire is connected ?"

Yes, that's the way to go. You set a default value for the control in question (any unreasonable value will do...). In the vi you check for the default value. When the value is different, a wire is connected in the main vi...

[DFGray]

Interesting post, but not necessarily germane to the discussion.  It was about multi-element queues, not single-element queues, so there is a memory management component thrown in.  I have not benchmarked single-element queues vs. action engines in a parallel environment.  My benchmarks were all single-threaded.  Multi-threading would be an interesting test. I will have to think about that when I update the data for LabVIEW 2009 (it is looking very good so far!).

As a side note, you can use the Windows tick counter to get sub-microsecond resolution in timing on Windows.  You have to run a few times and take the shortest measurement to ensure that nothing else happens between your timers.  If your time is over one OS slice time, you have to be really careful.

[DFGray]

Gee, Ben, you must have been really behind the times.  We moved from PDP-11 assembly to DECUS C about 1985

[Coq_Rouge]

---

DFGray wrote:
Gee, Ben, you must have been really behind the times.  We moved from PDP-11 assembly to DECUS C about 1985

---

I hope this was a joke. Because the need for assembly language will first die, then the last CPU in the world is destroyed. Assembly language has specific niche uses where it is important. Assembly language is still taught in most Computer Science and Electronic Engineering programs. Although few programmers today regularly work with assembly language as a tool, the underlying concepts remain very important. Having some basic assembly will make a far better programmer. In sharp contrast to say the Express VI concept which only contributing to stupidity among programmers 

[Ben]

---

Coq rouge wrote:

---

DFGray wrote:
Gee, Ben, you must have been really behind the times.  We moved from PDP-11 assembly to DECUS C about 1985

---

I hope this was a joke. Because the need for assembly language will f