LabVIEW
Handling time changes when graphing existing data
You can use the event structure to capture the cursor release and use that to index the timestamp and show it as either a popup or as annotation.
@SteveC_43 wrote:Another ignorant question. What's the best way to get the time stamp to appear on the graph in the first place since my event sequence number (reference number) is now the X axis label? Can you add text to a cursor?
Thanks for your help so far.
You can change the cursor name after you let the cursor go. Just make sure to make the cursor mode anything other than "free".
Actually using an annotation is better - changing the name of the plot will be problematic if you ever want to reference the plot by name (which is almost certain).
I have no idea what i was thinking in the post above - yeesh.
@drjdpowell wrote:You could avoid the problem entirely if instead of a "sequence index" and a User-made-up pretend time, you recorded the actual time.
Except for those darned, pesky customer requirements. 😄
@SteveC_43 wrote:It's never a pretend time. Ever heard of daylight savings? How about a system we send to Europe with existing data and they want to change a time or date? The only way to tie everything together is to NOT do it by date/time or it get's incredibly messy. Otherwise you get duplicate times and you don't know which time is the correct one to tie events to.
That system, which creates the files I'm reading, was written by very good programers with years of experience writing code for stuff you may use (or drive) every day. They don't just make stuff up or pretend.
Maybe you were just being humorous. If so, just ignore me. 🙂
Your first post implied a whole lot by describing everything with minute detail. It seemed that there was already a well established "way of doing things", if not actually established by customer requirement.
I'm sure that @drjdpowell didn't pick up on that. That's why I had the big smiley at the end. 🙂
