b_p

This partly sound like something I've been discussing with my boss for quite some time.

We're using our own dll - some thoughts on the dll + parser (I'm working in computer vision /inline inspection, which strongly influences my priorities)

a) multithreaded db write (we're solving this with multiple files, see b))

b) time / resource critical (predefined error codes, debugging levels, duplication filters)

c) clever real-time/rolling tailing / filtering

d) push-mode (email, text message) at critical errors in production systems

We're implementing our dll as a c-dll (LV is not our only framework) and I (as the LV nerd) am going to distribute a mnu (as soon as my to-do list allows/the boss bugs me too much). This mnu includes a "send warning/error/info", "send string", "make screenshot" "save config-files" and possibly (at some later point) a trace tool that automatically scripts a "write state info if DEBUG-environment-variable=1" into each file of a project.

I can't supply all of the above code because of my boss, but I am very willing to help with this project and strongly interested in some other parts, too.

I'm using LV2010.

Birgit

Just to add my personal solution to this, as I've stumbled over the same problem, found this web site and a solution while this tab was still open: Go to the bottom left of your front panel, there will be something like "Evalution" or "My computer" or "Main application instance". Switch.