Custom dynamic messages, and timestamp in error clusters ....

[manu.NET]

It should be nice to add custom message to the error cluster.

When you use the codified error codes, you cannot use dynamic error messages like : "File XXXX not found !"

So it would be easier to build more "user friendly error messages" ...

An additional Timestamp would also be usefull !

Something like this ....

To bypass this, i personnaly concatenate my custom error message to the error source.

It's not terrible ... but i have no other choice !

[smercurio_fc]

While it would be quite nice to have a more useful error cluster, I don't see this happening, given that it would break just about everything. Perhaps a new, separate error cluster could be introduced and it would only be available for new LabVIEW versions. If saving for a previous version it would get replaced with the "old" error cluster. But now you run into the problem of wiring this new error cluster to a VI or function that still uses the old error cluster.

This would also start a separate discussion on what should be in the error cluster. You don't want to put everything in there, including the kitchen sink. I had developed a set of VIs for the code I write that revolve around a cluster that contains an error status, a code, an error type (e.g., "warning" or "error" or whatever else you want), source, command sequence, reasons for error, and possible advice. I use an "Error Packager" that accepts a standard error cluster and basically packages all this information so it can shuttled around within the error cluster's source element. The library can also handle tracking of multiple errors. This was not something that was developed overnight. It was developed over many years, as this subject is fraught with challenges.

You may want to take a look at some of the work being done here.

[manu.NET]

The solution of the problem could be to create an "Error Object" instead of an "Error cluster"

The basic error Object could then be derived (Inheritance), specialised for every particularities.

[crelf]

You guys are on the right track - have a look at http://lavag.org/topic/10741-updating-the-labview-error-handling-core/ - it discusses embedding an "Error Object" *in* the "Error cluster".

[AristosQueue (NI)]

You already can add custom info to the error message. In the "Source" string, you can use the <err> and <append> tags. So if you have Error code 7 and source string "Somewhere on my diagram<append>XYZ.txt", you'll get

Problem at: 

Somewhere on my diagram

Possible reason:

File not found

XYZ.txt

[AristosQueue (NI)]

Forgot to mention... the <append> tag adds to the description of the error code as it is in the error code database. The <err> tag replaces the description entirely.  The only other tag that can be embedded is <b> and </b> to make some text boldface.

Message Edited by Aristos Queue on 02-15-2010 01:07 PM

[Darren]

Any idea that has received less than 6 kudos within 6 years after posting will be automatically declined.