how to programmatically check the error messages of a broken vi using labview scripting

[socalscouser]

hi Folks,

I'm basically trying to write some code which checks for broken vis in a folder and show the error in the broken vis. i got the part which detects broken vis but cant get the part which shows the error in the broken vi. is there a way to detect this? greatly appreciate the help. 

-S

[paul_cardinale]

[Sam_Sharp]

Out of curiosity, what does the 'Call Dangerously?' parameter do? I like to live dangerously, I can't help but feel like I would need to set it to true in all instances! (Like having a button that says 'Do not push'!!)

[paul_cardinale]

[socalscouser]

i cant seem to find this method for some reason. is there something that needs to be done?

[paul_cardinale]

You can just drag the snipet onto a block diagram.

Or add these to LabVIEW.ini:

SuperPrivateScriptingFeatureVisible=True
SuperPrivateSpecialStuff=TRUE
SuperSecretPrivateSpecialStuff=True

[Hooovahh]

---

@Sam_Sharp wrote:

Like having a button that says 'Do not push'!!

---

BTW the LabVIEW Wiki has been down for some time so I can't look it up, but is there actually a difference in those 3 INI keys?  The only one I know of that actually does something is the SuperSecretPrivateSpecialStuff which enables private methods, properties, and adds a few new events in the event structure.

[paul_cardinale]

I think some of them were for earlier versions of LV.  I haven't really kept track of them, I just keep them all turned on (plus some others).

[paul_cardinale]

Here's your unpushable boolean:

[socalscouser]

Paul,

that worked. thanks a lot. have a question though. is this invoke node part of scripting? I see that one of the variables had scripting in it.

also, i need to mass deploy this on many machines and so would have to add these variables on the ini files of all the machines ( which can be done) . but wanted to know if there was any other way to do this?