Rube Goldberg Code

[SteveChandler]

I don't know. Even though this has nothing to do with LabVIEW (or software at all) this just somehow seems to belong here.

[GregFreeman]

Have to assume this post could be cleaned up much further using in range and coerce.

[RavensFan]

I wouldn't call that a Rube.  The wiring could be cleaner.  And there may be a way to tighten it up by rearranging a few math operations.

If you think an In Range and Coerce really cleans it up, please post an example showing that.

[JÞB]

Hmmm. Count the keystrokes----

R-G = Text?

[SteveChandler]

You have GOT to see this post on Lava!

[tst]

You'll note that I also provided a link to the source, which has some more stuff - http://lavag.org/topic/10670-wired-wires/

[SteveChandler]

I saw the link after I posted. Now that is some REALLY cool stuff. I especially liked this one!

[altenbach]

I wonder how long it took to wire all this up... (only part of the diagram is shown! 🐵

All I know is that it took me ~60 seconds to do the same functionality from scratch... 😄

(seen here)

[RayFarmer]

Why the loop? If you needed a loop use an Event. Pointless having it loop if nothing is changing.

[altenbach]

---

@Ray Farmer wrote:

Why the loop?

---

The original code has a loop around it (no wait) so changes in the controls are updated. I guess it got clipped in the image above, but feel free to look at the original link. I retained that feature.

Yes, for a more polished application, an event structure should be used, but this is just a simple code demo. Introducing an event structure would have cost another two minutes of coding, would have confused the newcomer by introducing an unrelated new element, and would have taken attention away from the answer to the actual question. Let's not complicate things! 🙂