BreakPoint
Rube Goldberg Code
altenbach wrote:
Random sightings....
Ah, Altenbach, again you show how you just don't understand computers. This is clearly done because the value is also changed elsewhere and the new value is written between the writing in the top terminal and the reading in the low terminal. I mean, come on.
tst wrote:
altenbach wrote:
Random sightings....
Ah, Altenbach, again you show how you just don't understand computers. This is clearly done because the value is also changed elsewhere and the new value is written between the writing in the top terminal and the reading in the low terminal. I mean, come on.
Concidering that there an outstanding bug where LV is NOT doing all of the property stuff in a single switch to the UI thread, your description could actually occur!
Ben
LabVIEW user groep 
To allow an angle setting with either a numeric control or a set of 66 LEDs, we could code it with:
- 600+ local variables
- 67+ event cases
- 67 case structures, one with 66 cases that will never match because of FP math)
- hundreds of diagram constants
- a couple of days of coding
- a couple of days of debugging, because some boolean diagram constant got accidentally clicked/switched.
or we could get away with:
- 2 local variables
- 2 event cases
- no case structures
- one diagram constant
- a few minutes of coding (slowest step is arranging the 66LEDs in the radio control, that will still take a while without scripting)
- no debugging.
If our salary depends on the number of locals, the first solution is preferred. 😄
(read more here)
Well, we have 4 outputs and only 2 are used. That's exactly 50% for me. 😄
The problem is less well defined if we want to express it in terms of array contents. In the special case of an input array with two elements it would be 50% of the array contents and with an input array containing only one element, we would throw away 100% overall. There is nothing left at the end.
We don't know what the compiler does, it might not even generate the values for the disconnected outputs. Who knows? 😉
Of course you can use a pair of pliers to loosen a bolt, a knife to tighten a screw, a blowtorch to heat your lunch, or a Mack truck to get coffee. It still does not make it the right tool. 😄
The array tools are often incorrectly used. This is along the same lines of using "delete from array" to take a subset. We see that all the time here. 😮
Rob, real programmers use butterflies!
Of course, if you set the explosives just right, they should move the mouse by as much as you want.
This weekend I picked up this golden nugget from the Labview forum. I have decided not to disclose the user behind it. I have not even decoded the function. But it has something to do with selecting time intervals in a random fashion. I have programmed a Cray supercomputer to decode the function. And I will have an answer next week perhaps. In the meantime I will give kudos to all users who are able to solve the problem. I guess even the programmer behind it, is somewhat uncertain about the function. I quote
“Hi,
I have found a solution but it is very heavy, with multiple case structure. I guess that it will work but it is very difficult to check if there is no mistake”
I have posted it as I found it on this forum. It is quite large The top level VI is "essai VI 30.vi" Have fun