Ok, I will try to use as few words as possible to describe my application!
I wrote a wrapper for .NET DLL since it was returning an event source of 0 for call-backs and LabView doesn't respond to those events! Wow, was that a nightmare to figure out! The wrapper just "retransmits" the events. It doesn't even do any configuration of the library!
I'm having an issue where events seem to be buffered when my VI does things with front panel controls. It is strange since it seems one type of event isn't buffered and all of the others are, but that could be my perception.
I have front panel controls that are written to by passing a control reference to the "Reg Event Callback". I have about 30 events per second comming from three sources (90-100 events per second total).
Does anyone have any idea why my events would be "buffered" for up to a few seconds? I can cover the eye tracking sensor and see a playback record of the events! Slowing down could include something as simple as writing to a plot control at about 100 measurements per second. It is especially slow when the X scale is compressing to fill up the whole history. I've noticed that some controls are extremely slow, like sliders. I set the priority to the highest and changed the execution system, but I'm guessing this doesn't impact writing to front panels? I've also tried resizing the window so that the control that the callback is writing to isn't visible (this DOES make a program faster if you are writing fast to a slider) but it didn't change anything.
I've attached some snippets and my wrapper.
"Callback.png" is my callback function. All of the vis in it only include a few multiply/divide functions.
"Register.png" is how I register for the event and it shows the control that the call-back writes to.
"Program.png" is what my program does after registering for all of the events!
I will have to reply to this thread with the wrapper. Not enough attachments left!