Leaderboard

I'd like to think us at LAVA are better than Apple, Google, and Microsoft...okay maybe not better but something.

We deprecated those VIs in LabVIEW 2015 and created new ones that use error in/error out instead of embedded error handlers:

If the user makes a mistake it is an error (on the users part). If it he needs to interpret a 20 GB log file to guess why, then that's an uncaught error with no recovery (on the programmers part). I always say, errors are for programmers only because users just want software that works-preferably with one button "Start". As a user of your software I do''t want to be "trained" how to interpret your logs of gibberish or wade through reams of irrelevance to find out what to wiggle. I want to know whats wrong and what to wiggle so it works. Well. Changing a background colour doesn't require pre-defined controls on the front panel and is supported by all controls/indicators. I'm not sure how you used an image but I would imagine it needed an image control next to each unless it was a list/tree or something. You can get (and save) lists of the controls and limits (from your database ) and have a generic check/set that just iterates over the visible controls and sets the colour and limits. This enables you to also tell the user why the value they entered is incorrect if it's outside limits and what is acceptable to enter. See the "Panel Settings Example" to see how this might work. The cluster? For me, no. That's used also for sequencing.

Yup, wire a string or a path to the VI Path terminal and it accepts either. The VI name needs to be the full qualified name including libraries, but the VI Name property node returns it in this form.

I think it's polymorphic. Try wiring a string to the path input.