Rube Goldberg Code

[altenbach]

Most of us know Jim code quality well enough to instantly recognize what the intent was here.

(If a new user would have posted that, the situation would not be that clear. ;))

Still, a mention belongs into the RG thread, because that's what it is.

[tst]

---

@jcarmody wrote:

Is the rest of my participation in these fora of such poor quality that the intent behind this snippet wasn't obvious? 😞

---

Yes?

😄

Sorry, I tend to be stingy with my emoticons and I figured it was clear from the kudos remark that I got this.

Besides, I was talking about the other Jim... 😉

[Hornless.Rhino]

You could save BD space by using a stacked sequence structure. 😉

[James_W]

I do have to admit I did love reading that thread. Especially when James and Chris suggested thier 'mods'. Although I was concerned that Jim's 'Plugin' only seemed to work on the Queue and not on all wires!

Loved the code Jim - pretty much as normal for your stuff. (Except I'm not normally laughing at/with it.)

James

[tst]

BTW, I love the second for loop:

[JÞB]

---

@tst wrote:

BTW, I love the second for loop:

---

That guy must get paid by the wire!  Second loop!  What's with the second FRAME? and why the string indicators?

[James_W]

You obviously haven't bothered to read the thread that Jim pointed to then Jeff

[VDB_1]

World's Slowest Rube Goldberg   No LabVIEW involved though...

https://www.youtube.com/watch?v=o-c7tBlnFsw

[BowenM]

No more stacked sequence structure?  No problem!

(not quite RG code, but...)

[Hooovahh]

I've seen this technique and don't hate it if you modify it to use a 1D array of strings that get auto indexed into the for loop.  Then the cases can be named and reused.  Still not as flexible as a proper state machine but still simple and easy.