User | Kudos |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |
Can you venture a guess what's wrong with this diagram?
Well, you could, but there's no way you can be guaranteed to guess all of the problems.
The answer is that N3 will show the value of X+Y (not X*Y, since there's an add primitive under there which you can't see) and that N4 will show the value of Y.
The problem here is that LV allows us to let things overlap. This is great if you want to write obfuscated code, but has no practical use in the real world. So my idea - BREAK THE VI if nodes, wires or tunnels overlap "too much" *. Today, LV already gives you a warning for some of these, but most people don't have warnings turned on and don't look at them.
While having overlapping objects does not directly affect whether the VI can execute or not, and while I do realize that this is an extreme change in behavior, it is enough of a source of potential bugs that I feel this change is warranted. Maybe NI has some info about how much something like this would be useful or annoy users.
* No, I don't know what "too much" is and I normally don't overlap things myself, but it can happen accidentally and I do get code from other people which does have this to a degree.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.