LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
hunter_jki

Flush Event Queue Should Return the Data!!

Status: New

Currently if you flush an event queue that data is lost. Flushing and destroying and event queue should have the same interface as flushing/destroying a normal queue. Return the Data! I want the option to batch process the events, The code below would have to handle 1000 separate events to get the data out.


hunter_jki_0-1672775860961.png

 



Idea
Flush Event Queue.vi should return remaining event data.
Destroy User Event.vi should return any unhandled events.

2 Comments
McQuillan
Active Participant

I don't think Destroy User Event should return unhandled events as it is down to the specific event register(s), as to what is/is not handled. Perhaps getting the data at Unregister Event would be more helpful.

 

But returning data on the Flush Event Queue would be handy.

hunter_jki
Member

@ McQuillan Good point, I mostly tossed that in so it matched the queue API. All I really want is the flush return 🙂

Destroy could return events handled by no one (I think the overwhelming majority use case is a single registerer), multiple registerers makes the output more complicated for the corner cases.