LabVIEW
Scripting with Error Rings
@paul_a_cardinale wrote:
Scripting with Error Rings (new in LV 2012) is possible, but it's a bit tricky. The attached .llb makes things a little simpler.
(Some of the code is so ugly, I locked the BDs.)
Rspectfully, why would I use something that someone I don't know uploaded and that I cannot look at the source code? Also, if I can't look at the block diagram, how am I to know whether or not your solution is better than mine?
You'd probably get a much warmer response if you opened up the library for inspection. It's executable code - people are going to want to know what they are executing. 🙂
@paul_a_cardinale wrote:
Most of the BDs are open. The only ones that are locked are simple wrappers for "L10N.vi", "Update Error Description.vi", & "Get All Errors In Family.vi" in ...\vi.lib\ErrorRing\Utility\.
Those Vis have private scope, and you're not supposed to be able to call them. I found a way to call them, but thought it would be a bad idea to disseminate that into.
I think you need to see this from a user's perspective. For the same reason I don't click on links or open files with execution potential in email, I won't execute a VI that has "secrets."
Besides, if you think something is "bad," what makes you think it's "good" for public consumption? 😉
