Project context aware custom errors

[sthomas]

The error ring is a handy tool I've just learned about.  It would be fantastic to be able to create an error ring for a project that can be type defined to easily distribute with applications.  This way all custom error codes for a project may be easily stored with all the project files without having to worry about including a file from the user.lib.  Other ring controls/constants/indicators can be type defined, why can't the error ring?

[Mads]

Editing custom errors directly in the error ring constant is quick and easy. You can add formatting and the node will automagically add inputs accordingly...All we really need is for the errors to be accessible from any error ring constant in the project and voila. All the upsides of custom error files can be included in this functionality - without the downsides - and with extra upsides(!). There are plenty of threads on ni.com and elsewhere pointing out all the negative sides of the user defined error codes file handling so no need to act as if it is a good solution, just to shoot down this idea.

With custom errors defined globally within the project like this (frankly I was very surprised that this was not the way it worked in the first place) you do not need to bother managing an error file unless you want to (the fact that you have to store it in your LabVIEW installation makes SCC more hassle too - hell, if you wanted you could always make LabVIEW have a feature to automatically generate that file and store it somewhere *you* want too).

I suspect the only reason this idea has not got more kudos is because so few people know about the nice but crippled customization feature built into the error ring constant.