LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
Showing results for 
Search instead for 
Did you mean: 

Advanced Error Cluster with more intuitive handling

Status: Declined

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

There was already a suggestion to improve the error cluster (here). I want to go some steps further in comparison to this idea.


Part 1: Information in the "advanced error cluster":


advanced error cluster.png


New elements would be "severity" and "error occurred at time".


Part 2: Behavior of the "advanced error cluster":


I think the best approach for the new error cluster would be to have it like the Dynamic Data Type, which was introduced with LV Express (7.0).


a) Compatibility to the "old error cluster":

If you wire the advanced error cluster to an old one, it would automatically create a "From Advanced Error Cluster"/"To Advanced Error Cluster". This would enable working with both clusters in parallel to keep downward compatibility.

Sure, "From Advanced Error Cluster" would remove the newly added information from the error wire. This is some caveat/downside when working with "old" functions.


b) Connecting a source of an advanced error cluster wire to an existing wire of the type would create a Merge Errors automatically. Wiring additional (advanced) error clusters on the input side of this Merge Errors would increase the number of inputs accordingly.


c) If two or more inputs of the Merge Errors function would carry an error information, the output would be a single advanced error cluster with the error information of the error input containing the highest severity.


Part 3: Possible new features for "advanced error cluster":


Esp. severity could enable good "default" functionality which could be enabled/disabled in the LV settings. Something coming into mind is:


a) Log Error: All errors are logged in a preconfigured error log file when they occur.


b) Log and Discard Low Severity: Errors which occur with Low severity are automatically logged into a preconfigured error log file and then discarded (removed from the wire).



Part 4: Other suggestion already made in regard to Error Handling:


Specific Error Handler


Object Orientated Error Handler



Feel free to add comments in order to create an "comprehensive list of error handling strategies" in order to pick the most promising for future LV features.

CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Knight of NI

I don't like the idea of making the severity an enum. Your list of severity levels may be different from mine. 


For comparison/alternate idea, the error cluster I use in the error handling routines I wrote (which are compatible with the existing error cluster) looks like this:


ERROR - Support CTL - Error Info.ctl_FP.png



I assume this new error cluster would still employ the silly convention of warnings being the status = False and the error code being non-zero? (I just love bringing this up all the time. It's one of my pet peeves, so don't take it too seriously.)


Knight of NI Knight of NI
Knight of NI

The new error "cluster" should definitely be a class, to allow for extensibility.


In any case, I don't think the idea exchange is a good place to discuss this. Its interface is extremely unsuitable for such a discussion. The LAVA thread you linked to is a valid place for such a discussion.


In any case, a new error handling framework should probably also ship with some additional tools for error handling (such as templates, loggers, examples, etc.).

Try to take over the world!
Proven Zealot
Classes or leave it as it is please.....
Proven Zealot
Status changed to: Declined

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

DNatt, NI