User | Kudos |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |
Hi,
NI could organize the error numbers into trees of relevance according to tags assigned to each error either by NI or by us.
Thus, we could say that errors x, y and z are related to missing files, for example, and that a, b and z relate to TDMS files.
Once this is done we could use a new ignore error block that will ignore families of errors instead of specific errors.
Many times you don't know which errors could come out of your code but you might be able to handle general common issues even if you don't know the specific error number you'll get for them.
Moreover, each error you customize and create could get it's own tag from the general list or from a new tag you create.
This will organize the errors and help users better understand which errors are already available.
It is sort of an OO Error System.
One error could appear in several red/black trees so the search could be fast and a user could even ignore errors that answer to the cut between several families of error (related to both TDMS and to missing files).
Dror.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.