I just put together an animated bargraph to show results from a realtime
process.
I used this as an example:
http://matplotlib.sourceforge.net/examples/animation/animation_blit_qt4.html
The tricky part for me was that in the original design, there was a realtime
process running. I have to write some information to my hardware (at a rate of
about 1/360ms). To do this, I have a kernel driver that uses 'read' to tell the
user space when an interrupt has occurred, which is when the user space should
write new information to the hardware.
So I don't know how or if this could be hooked into qt event processing. Just
for a quick-and-dirty demo, I just removed the realtime processing from the
user-space and put it in the kernel driver, so now my bargraph display can
simply update on a periodic timer, and the userspace code has no realtime
requirement. But this is just a kludge.
So I wonder how other's would solve this? I'm thinking it would be either:
1) multi-process
2) multi-thread
3) 1 process, but somehow hook my realtime events into qt's event loop.
For #3, my device driver has a filedescriptor, that could use select to detect
the interrupt (rather than blocking read call).
#1 and #2 seem complicated.