Rube Goldberg Code

[crossrulz]

If you want to see some bad LabVIEW drivers, take a look at Excalibur's 1553 drivers.  They are pretty much DLL wrappers, but they are still so horribly written.  I ended up redoing a bunch of them.  The main offender for those were the fact that every VI had the same icon.  So you had no clue which VI was being called.

[JÞB]

You submitted feedback to the IDN Right?  They do respond to your concerns when you hit that button.

[Ray.R]

---

@thoult wrote:

---

That's beyond Rube Goldberg code!!  That's just wrong!!  .......     okay...  yeah...  it is RG code...   Those SSS can be nasty and this is a fine example of it.

[JÞB]

---

@Ray.R wrote:

---

@thoult wrote:

---

That's beyond Rube Goldberg code!!  That's just wrong!!  .......     okay...  yeah...  it is RG code...   Those SSS can be nasty and this is a fine example of it.

---

How many times do we need to disable all those controls in a greedy loop?  That CORE is smoking hot!  Can the mouse even move to click Stop?

[Ray.R]

I know...

My original reply was that of a "Grumpy Old Man"...  So I changed it to something...  well.. boring  politically correct..Just how many times do you need to disable a control?  Once every millisecond?  And then do it again if you start a cycle (run the code, etc).  And what's up with those Local Variables (Axis)?  Nice straight wires would do the trick..  No visible race condition, but it would reduce congestion in the Case Statement.

Of course, I have not seen the rest of the code. 

[thoult]

---

@Ray.R wrote:

Of course, I have not seen the rest of the code. 

---

Lucky you - there are some things you just can't unsee

[altenbach]

Another public message from the "Complex is Simpler" department. (Seen here)

It is a good programming exercise to display an analog clock using an xy graph. try it!

(Yes, using a gauge with three hands would be simpler, but let's keep the front panel the same).

However, why would it need

• three stacked while loops???
• six simulate signal express VIs???
• dynamic data???
• 5 shift registers???
• three case structure???
• 3 comparison operations???
• building arrays?
• bundling clusters?
• etc.

(top image)

If all that's really needed is a small while loop and a little bit of code (bottom image). 😄

[Andrey_Dmitriev]

---

@altenbach wrote:

Another public message from the "Complex is Simpler" department. (Seen here)

It is a good programming exercise to display an analog clock using an xy graph. try it!

---

The are are no limits for simplification

[altenbach]

---

@Andrey_Dmitriev wrote:

---

@altenbach wrote:

Another public message from the "Complex is Simpler" department. (Seen here)

It is a good programming exercise to display an analog clock using an xy graph. try it!

---

The are are no limits for simplification

---

Well, 3014kb >> 20kb. Arguably, 20kb of code is "simpler".:D

In fact, your "simplicity" is only achieved after the fact, because you needed my full code to generate the diagram constant in the first place.  Your code would require significant and complicated effort to be generated starting with a blank VI. 😮

OTOH, I use lookup tables very often in my own code. They are often great! 😉

[Andrey_Dmitriev]

---

altenbach wrote:

Well, 3014kb >> 20kb. Arguably, 20kb of code is "simpler".:D

---

The code was only 3.5 KB, but the data - you're right. Yeah, simplification is sometimes compromise...