> You will find that in Labview, the squeaky wheel gets the grease! > Until recently, EVENTS in Labview were treated as ugly children, now, > the entire architecture of Labview is event driven. This change was > brought about only because of vocal popular demand. I believe more > input from users like you (and ME!) will eventually do for TIME what > we've done for EVENTS.
While feedback is always welcome, just to be clear, I think stating that the entire architecture is now based upon events is a bit much. In fact, the marrying of events with dataflow was a bit tricky, and I'm pretty happy with how it turned out, but LV is still very much a dataflow environment. Events are there to help out with UI, and the other synchronization primitives that were already there are now supplemented by user events. User events are pretty much notifiers that feed into the event structure. As for time, in LV7.1 I believe the timestamp is now a 128 bit integer that measures on a much finer time resolution and for a much larger scale. This should work well for HW timed measurements. Of course the other time systems, including the ones the system and Excel use will still be with us. If you or anyone else has more concrete suggestions, please let us know about them, here or better yet in a suggestion form. Greg McKaskle
