Leaderboard

Mwuhahahahaha! Three config tokens have escaped your grasp! I modified them specifically for folks like Flarn! They don't appear as plain text anywhere in the EXE (or in any VI for that matter). Do they guard any great secret of LabVIEW? I'm not telling! But you can have fun pouring through the code and looking for interesting bits and trying to figure out what you need to put in your config file. LabVIEW 2013 or later. Good luck.

Every time I read "brown nodes" I think of this unicode character... Not that they are bad, they just shouldn't be there.

While that is true, the property and method menus do get rather messy and unstructured when this is enabled so for normal development work I definitely prefer this option to be disabled. YMMV if all you do with LabVIEW is digging for rusty nails and other attic relicts.

“sub-level†VIs? You’re going to have confusion regards, as “top level†can refer to more than one dependance hierarchy. Something started by an ACBR node is “top level†in one sense but not in another.

Keep It Simple. If it has a block diagram (or at least compiled code), it's a VI. If a VI is run at the top level, it's a top-level-VI. If a VI is called by another VI, it's a sub-VI. If a VI has a front panel that is presented to the user, it's a UI-VI. Or an interactive-VI. Or a user-VI. But they're all VIs, the other names just give hints as to how the VI is used.

Hi, Your understanding of "." and ".." is correct, don't worry LabVIEW treats library files as folders. The URLs are relative to the "inside" of that folder. Notice that: The class private data's URL is "Setting Element.ctl" (no "../"!) The VI's URL is "../Pseudo Array - Remove Row.vi" Where are the .ctl file and the .vi file on disk? The .ctl file is embedded inside the .lvclass file. The .vi file is not embedded -- instead, it lives one level above the .ctl file, on the same level as the .lvclass file.

No, they aren't checked at startup. And that's as much help as you'll get from me. :-)

It's a gift. Or at least you should look at it like that. I call it the Aura of Technical Doom - an innate ability to break anything technical sometimes just by mere presence. If you are a quality engineer with this special power, you are feared by corner-cutting engineers far and wide. These special people are also the bane of demonstrations and usually illicit the phrase "it was working earlier" from other engineers and sales people

In a few years you will have enough to make a Quilt or better yet a Cape (Champion CRELF)