Anke Schenk

QUOTE (Bjarne Joergensen @ Feb 26 2009, 06:12 PM) Bjarne, My best used tool is the "Total Commander" by Christian Ghisler ( a must have for anyone who once used the Norton Commander). The built in search command works just fine. I don't know about other browsers. hope this helps regards Anke

Bjarne, I don't know about LV Versions above 7.1, but until then a simple text search for the Vi name whithin the xxx.vi files does help. Anke

Hi Mike, there is an old collection of Windows Utilities on the NI website. A VI from the winevent.llb might do the trick. Anke

QUOTE (X_DOT @ Dec 12 2008, 01:11 PM) Jens, Why do you store the timestamps as strings? If you keep the original timestamps in your array, you can use the "subtract" function and get the time difference in seconds. In this case you will only have to convert the timestamps into strings just before displaying them. hope this helps Anke

One of my favorite Vis is called ToDo. It's function ist to do nothing at all, but exist anywhere on a BD where there is some work left unfinished. It has a bright red icon and a required text input to describe whatever there is left to do. It is an eyecatcher on any BD and easyly spotted in the hierarchy window. A search for all occurrences of this Vi will show you all unfinished parts of your application at a single glance.

In the last example you made quite substantial changes to your first design and I think that way it looses much of its original charme. I believe that is not necessary at all. I tried to make your VIs work, just handling the user event separately, as I described in my first post. Nothing else in the structure had to be changed. Please have a look at my modifications (I am sorry but I left your comments on the main VIs front panel). Download File:post-3175-1134505566.llb Anke

Don, I had a try at your example and found, that the user event does never fire in the main.vi as long the sub.vi is runnig. Triggering in the sub.vi does not make any difference. The reason for that behaviour is actually rather simple: 1. There are 2 user events, let me call them "stop" and "invert" for short. 2. There are 2 event structures, one in the main.vi the other in the sub.vi. 3. The "stop" event is to fire in the sub.vi event structure. 4. The "invert" event is to fire in the main.vi event structure - which it refuses to do. In your example you registered both events with both event structures. You get the idea ? If you separate the events and only register each event to the one event structure it is supposed to fire things will work just as you described them in the first place! Anke