Make it posible to find error codes in help.

[Yakov]

Just that: Make it posible to find error codes in help.

I can never find general list of error codes wigh their descriptions in the Labview Help.

[crossrulz]

There is the Help->Explain Error menu item.

The real problem here is that you have different error codes for different modules inside of LabVIEW.  I imagine it could still be done.

[StephenB]

What would really be nice is if functions documented which error codes they could throw

[crossrulz]

You mean like this idea: List every error code a function can give out!

[AristosQueue (NI)]

Yakov: There is no list because the list is open-ended and shifts depending upon what modules you have installed. If you want to see a list of the error codes, open up the *-errors.txt files that are on your disk. The ones in <labview>\resource\errors are the ones for LV core. The ones in <labview>\user.lib\errors are installed by third-party libraries. The ones in C:\Program Files\National Instruments\Shared\Errors\ are from hardware drivers. Collectively these define the error codes on your particular system.

[Yakov]

What I mean is, when I go to help to look up error codes I get this:

... and none of the topics give list of error codes of any kind.

I would like to see something like this:

and if I open the page:

... here we go. Error Codes!

So in Labview Help for "error codes" the topics should be:

General Error Codes

Networking Error Codes

DAQmx Error Codes

Vision Acquisition Error Codes

...

...

...

[AristosQueue (NI)]

That file is in the index.

[AristosQueue (NI)]

There is no list of errors from the other modules because when LV ships, we don't know those errors. Each module/toolkit (including from third-parties) can install additional errors. That's why if you want this information, I was pointing you toward the error code text files.

[Darren]

Perhaps the best solution here is a dynamically generated list of codes and descriptions based on what is present on the system. It seems like we could provide a Help menu option that runs a VI and generates a dynamic HTML page with that info.

Yakov, given what AristosQueue said about the dynamic nature of the errors.txt files on the system, would a separate tool to generate information about locally-installed errors be a viable solution?

[JÞB]

Darren

"Perhaps the best solution here is a dynamically generated list of codes and descriptions based on what is present on the system. It seems like we could provide a Help menu option that runs a VI and generates a dynamic HTML page with that info."

---

You mean like the error ring (Perhaps searchable)

Whatever is going on behind the scenes in that select error dialog ALLREADY generates a dynamic list from whatever in installed- redirecting its output to a HTML file ought to be relatively painless (For me at least- maybe not for the developer) Unless.... Hmmm If you don't pick that up 8-Ball might, I like that idea

[johnsold]

Darren and Jeff,

Given the dynamic nature of error messages, the concept of a VI to get them sounds useful. Even better would be a list specific to a VI named (or by refnum) as an input to the Get Error Messages VI.

Go for it, Jeff.

Lynn