Rube Goldberg Code

[craigc]

Altenbach is that a coercion dot on your example of how to simplify a boolean array to string? yep i think it is...let me look closer...yep its still there 🙂

[altenbach]

---

craigc wrote:
Altenbach is that a coercion dot on your example of how to simplify a boolean array to string? yep i think it is...let me look closer...yep its still there 🙂

---

It's a "virtual coercion dot", because it shouldn't be there. This is a known bug in recent (8.5&8.6) versions, possibly only cosmetic. 🙂

Hopefully, it will disappear again in future LabVIEW version. 😄

[craigc]

Phew, i thought you might be ill or something. Glad to hear all is well 🙂

[altenbach]

Adding one to a wire can be done in many ways.

• Use the "+1" primitive.
• Use a "+" primitive and a "1" diagram constant.
• Use an expression node containing "x+1"
• ...

Of course none of these are really satisfactory solutions if we really like text based code. In this case we would do the following:

Why not use mathscript???? 

(spotted here)

Message Edited by altenbach on 11-18-2008 12:08 AM

[smercurio_fc]

I think they should have written a DLL.

Or, better yet, a web service. Hooked in with a mobile phone that uses 3G. Yeah, that's the ticket!

[altenbach]

So, we have a a few booleans and want to make an array.

First we need to read the locals, make each into an array with one element, index out the element, and built the array.

This route is too scenic for me! 😄 Can anybody guess what the idea was to do this in the first place????

(seen here)

Message Edited by altenbach on 11-19-2008 11:33 AM

[Intaris]

Wow.

I'm unable to come up with anything LIKE a logical reason for that code to exist.....

Shane.

PS Maybe he's a Tolkien fan with a very dry sense of humour.... "There and back again"

Message Edited by Intaris on 11-19-2008 03:28 PM

[RobCole]

Are you sure it wasn't just trying to waste a couple of cycles to adjust the timing?  (NOP)

 But even then... There are better ways of doing that.

     Rob

[Ben]

RE:

Crazy Idea Time!

Premise:

I can still rember geting started with LV. At that time I was quite mystified by the various operators and exactly what it was i was going when I wired things up. (Even worse than that I had trouble figure out what that weird icon [Wiring tool] was and were exactly the sweet spot was, but I digress). When I did get things wired such that there were no broken wires I would find myself silently cheering and due to the frustration did not stop to Q what it was that I did but was happy that the run arrow was not broken.

Idea:

It would be nice if LV had an option (that I could shut down as soon as I installed LV ) that would compose a narative similar to the comments you would find in an example VI (no not real comments, but thype of comments that focus on the operations being performed not the BIg Picture). While that option was active and the user was not actively editing, the region of the diagram where the mouse was located would display a tip-strip containing the the narative. In the cae above it would read as Christian wrote. By reading the "translation" of the code, new users could get a hint that they are not using the most efficiant approach.

Even if the tip-strip was limited to only inverse operators being wired together like the build followed by the index.

Just another crazy idea,

Ben

[RobCole]

Ben said:

... Even if the tip-strip was limited to only inverse operators being wired together...

 This sounds more like the kind of thing that you should find in the VI analyzer. Not that everyone uses the VI Analyzer even though it can be quite helpful.

     Rob