Quote:
Originally Posted by Joe Ross
Quote:
Originally Posted by Ether
An event handler, as I was using the phrase, is application-level code that gets executed when an external asynchronous hardware event occurs. The execution of this code is "managed" by LabVIEW/vxworks in the sense that resources are allocated to the handler based on time-sharing and priority of other tasks concurrently competing for resources.
|
I had assumed that the code the Greg posted worked this way and not that everything in side the while loop was running inside the ISR.
|
Perhaps Greg could confirm?
If so, back to my original suggestion: the 2010 Framework had "placeholders" for periodic tasks. Perhaps doing the same in the 2011 Framework for event handlers would be helpful. Users asking about "interrupts" could then be directed to the Framework's support for event handlers.