error handling

[billko]

---

@crossrulz wrote:

<snip>

 

The error ring works with the customized errors.  You just need to maintain your customer error files and the ring will work automagically.  BTW, the error ring is new to LV2012.

---

Are you sure about that?  I have an error ring constant in LV 7.1.  Maybe we aren't talking about the same thing?

[Mark_Yedinak]

---

@billko wrote:

---

@crossrulz wrote:

<snip>

 

The error ring works with the customized errors.  You just need to maintain your customer error files and the ring will work automagically.  BTW, the error ring is new to LV2012.

---

Are you sure about that?  I have an error ring constant in LV 7.1.  Maybe we aren't talking about the same thing?

---

The error ring was removed for a few releases. It was just added back in again in LV2012.

[JÞB]

I'm surprised you have it on a 7.1 BD the ring was demoted in 7.0.  Back then it was a static list that could not track errors imported with toolkits and drivers.  AQ got the nod to fix the ring to dynamically adapt to all errors that are maintained in C:\Program Files\National Instruments\Shared\Errors\

One of my favorite new features.

[billko]

---

@JÞB wrote:

I'm surprised you have it on a 7.1 BD the ring was demoted in 7.0.  Back then it was a static list that could not track errors imported with toolkits and drivers.  AQ got the nod to fix the ring to dynamically adapt to all errors that are maintained in C:\Program Files\National Instruments\Shared\Errors\

One of my favorite new features.

---

Wow!  It's a good thing I never used it.  😉

[JohnZ]

Why does the error ring behave differently if the error description is pulled from a custom error file versus being entered manually as a Custom Error Code?  The attached snippet and screenshot shows the results for two error ring examples.

Notice that the second error ring, where the description was entered manually, includes the description and the values of the three input parameters in the standard front panel error cluster display.

The first error ring, where the identical description was entered in a custom error file, does not include the description in the error cluster.  It does display the description in the Explain Error dialog box as shown in the screenshot, but it does not replace the formatting codes with the actual input parameter values.

Is there a way to get the error ring to properly display the description and input parameters when using a custom error file?  That is a much better way to maintain consistency across an application than having to manually enter the description and formatting codes every time.

Thanks,

John

[JohnZ]

Oops!  I included an old snippet and screenshot before I changed the input parameters to different types.  Here are the updated images using the same description string in the custom error file as was entered manually.

John

[Zach J]

Hi JohnZ,

At this point in time, if you are needing to actively update included information in an error ring, your manual formatting is the best method.  The custom error file is read in as a static piece of text to be displayed.  Therefore, any wired inputs that you may expect to be shown in the Error Details window will not display.  If you have an idea for making the custom error file a little more configurable, please feel free to post a new idea in our Idea Exchange on these forums or submit feedback about LabVIEW.  We are always actively looking for ways to make LabVIEW and our other products even better.