Rif.: Manage Error Codes of DQMH module

[FabiolaDelaCueva]

---

@Konan__ wrote:

---

---

---

Do you maintain a document will all error codes to avoid clashes?

We assign error ranges to each DQMH module. You know what are the DQMH module errors, because they are all VIs with the name --error.  No need for a central document, the information is within each library. I agree something more detailed could be added. Perhaps, you could add a feature request for Oliviers' Antidoc, that it lists all the --error VIs for each DQMH module. 

---

@Konan__ wrote:

---

---

With "Error VIs", the developer doesn't think about error codes, but error semantic.

Example: in the block diagram , I place a "Timeout---error.vi" or "Output1---error.vi", and I dont know that inside they have 500123, or 5123 error code.

So a central document is needed, unless one develop a custom solution like "error classters" of Dimitry. 

I figured out I am re-doing what he's doing.

Some years ago I asked if error cluster could be a class, but the idea was rejected. 

---

It was not completely rejected, Stephen Loftus-Mercer almost completed the implementation but they backtracked when they saw that reverse compatibility with existing code would be too hard. I believe he posted the code somewhere if you want to be the brave soul that adds it to your version of LabVIEW 😉

[FabiolaDelaCueva]

---

@Konan__ wrote:

@fabiola

another question on the topic

why

"Delacor_lib_QMH_Error Handler - Event Handling Loop.vi"

and

"Delacor_lib_QMH_Error Handler - Message Handling Loop.vi"

??

inside they are the same. Does it mean we should customize it? when?

I dont understand the rationale of this

---

Like Joerg mentioned, you can extend with your own child class.

Also, for DQMH 5.1, we are working on reporting where the error came from, in the case of the MHL, it will tell you which Message case reported the error. In the case of the Event Structure, it will tell you which Event Structure from which loop (in case it is coming from a helper loop and not the main EHL).

We left that for future expansion, we just had not gotten around to expand it until now but left the option in case you wanted to do it yourself before we were ready.

[joerg.hampel]

---

@FabiolaDelaCueva wrote:
which Event Structure from which loop (in case it is coming from a helper loop and not the main EHL)

---

😍

[Konan__]

---

@FabiolaDelaCueva  ha scritto:

---

We assign error ranges to each DQMH module. You know what are the DQMH module errors, because they are all VIs with the name --error.  No need for a central document, the information is within each library. I agree something more detailed could be added. Perhaps, you could add a feature request for Oliviers' Antidoc, that it lists all the --error VIs for each DQMH module. 

I appreciate the error detail you are developing in the 5.1 release.

I didnt know about this Antidoc project.... it seems good, but maybe overkill for me... What about putting all the --error VIs into a virtual "Errors" private folder (or "Module's Errors")? 

I think module's errors deserve a dedicate clear folder. It will also immediately show the developer your politic of managing errors. I am very experienced in LV but I never thought about making a VI for an error, and had to dig through the code, ask here, etc...

PS: I got the DQMH badge 🙂 but I can't put it in my signature (I copy pasted the html code but it's not rendered)

[FabiolaDelaCueva]

---

@Konan__ wrote:

---

... What about putting all the --error VIs into a virtual "Errors" private folder (or "Module's Errors")? 

That is a great suggestion, if you want, please add it to the DQMH feature requests:

https://forums.ni.com/t5/DQMH-Feature-Requests/idb-p/delacor-ideas

---

@Konan__ wrote:

---

PS: I got the DQMH badge 🙂 but I can't put it in my signature (I copy pasted the html code but it's not rendered)

---

Congratulations!

I use this HTML editor to preview signatures:

https://www.onlinehtmleditor.net/

I tried this text and it worked out:

<img src="https://images.youracclaim.com/size/340x340/images/ef19fb7b-e76c-4406-b1b4-96a40f42d84a/DQMH_Framewo..." alt="DQMH badge">

I will play with my signature later on to add the badge... but I better not go there now or there goes my productivity 😉