Attached is part of VI that I am trying to use for debugging purposes. Basically, it uses the Event Inspector to log almost all of the Event Data to a debugging log; the log also contain commands from various JKI State machines running. A sample of the log is below Time VI Command 2.647235 Main.vi Panel Close? Main.vi2.647235 Main.vi User Event Macro: Exit2.647235 Main.vi User Event Macro: Exit2.647235 UILoop.vi User Event Macro: Exit2.647639 Main.vi Macro: Exit2.647655 Main.vi Message: Exit I almost got the "Event Logger" portion working correctly, the only problem is the Event logger uses the millisecond timer whereas the other part of my debugger uses the high resolution seconds as a timer. (The millisecond timer does not have the resolution.) Anyway the attached VI is my attempt to parse the Event data in a way I can use it. It seems & looks cumbersome, and may even make the Rube Goldberg thread. I was wondering whether anyone had any optimizations they can suggest. I did not use regex because I thought that was the worst performer. Code snippet below, VI attached. Default values are included in the VI. Thanks mcduff

LabVIEW

Better Way to Parse Event Data

You can skip the fist two functions (outside the case structure) if Event Array is empty. Not sure how often that happens, it would depend on the application. If you poll those events more often then the events come in, it might help a bit. Depending on the benchmark mechanism, it might not show.

I'm not sure if your concern about reg.ex. is valid. That scan from string might be slow, and you still need two match patterns. The reg.ex. performance might surprise you, although the used query is significant.

As the scan from string mostly separates tabbed items, a spreadsheet string to array might be faster. That function goes like a rocket.