need suggestion on error treating strategy

[MaGH]

Hi, becktho,

yes, it's fantastic. It impressed me. I'll try it in my project/

Thank you!

[becktho]

Hi

Criticism is very useful, when constructiv.

Just to answer your comments dynamic:

1. The LV2 global allows me to be safe - if I used a normal global (what I did in an earlier version), I had to use semaphores to control access

2. Well, the numeric ones could also be handled using variants (nobody is perfect - me too ;)), but as this has grown this way I kept it

3. If you have a look at the file-entries in the file, you'll see that they do have a timestampt. Also the log-level and the error-causing module are written to the file. In addition - if the log-file exceeds 10MB, it is backuped (to either be deleted or reviewed at a later time)

Anyway - I'm glad if this tool could help some guys.

Thomas

[shoneill]

Hi Thomas,

another great contribution.  I've been thinking along these lines for quite a while now in order to enable "global" error handling in an application.

I always thought that it would be "frowned upon" to de-localise the error handling like this.

Hence my question:  Is this simply a logging feature, or is the error-handling also centralised?  I'm stuck in a timewarp on LV 6.1 so I can't test myself.

I suppose a multi-tiered approach could be used where a centralized threar controls the occurring errors and steers the "global" activities accordingly whereas the low-level error handling is still done locally.  I think there's a lot could be done with this approach.

As soon as I upgrade, I'll try out the software,

Shane.

[becktho]

Hi Shane

Thanks for the flowers :D. Have you been able to look at the code?

To answer your question: The purpose of this library is just to log statements.

[WNM]

---

@shoneill wrote:
 I'm stuck in a timewarp on LV 6.1 so I can't test myself.

---

In this case, sure you can. See if this helps.

[becktho]

Thanks warren for you assistance in conversion to previous LV versions ;).

[shoneill]

Thomas,

You're welcome.  And Warren, thanks for the conversion.  It's pretty neat, I must say.  I like the distinctive icons too, adds a nice touch.

Haven't had a chance to look through everything but I will definitely get around to it.

Shane.

[becktho]

Shane - any comments are welcome. Maybe I can improve it once more ;).

[Dynamik]

Sorry becktho..

I was working on about 6hrs sleep and 1 neuron.  The last thing I did before shutting-down was double-check for (and overlook) timestamps.

Nice work.

BTW, Here, Ben discusses "Mutex" - the newest  word in my vocabulary.

[Tushar_Jambhekar]

nice post.

In my projects i use a modified queued msg handler architecture, which helps me trap the errors as they occur. and the structure is very much simple, also it allows me to handle the errors (not just logging) with little modifications in the template.

the template also allows me to locate the area where the error ocuured first.

feedbacks are welcome.

this post has given me some new ideas and soon i will update my template to incorporate new features

you can find me template here

http://forums.ni.com/attachments/ni/170/146200/1/Tushar’s Template.zip