The visualization end should have been in mostly only one direction and pretty much non-blocking ( except for when you're out of data ).
The other side - configuring the hardware - is my bread and butter, and there are a few simple abstractions that are pretty old now ( I have been using them since the late '80s ) that will help greatly.
Sadly, for inexplicable economic reason(s), these are less well known year by year.
Also - for extra points, think about how you'd do that in one thread. Betcha can... although multiprocessor can be pretty cool. Now write it to where it doesn't matter if it's one or multiple threads...
My first inclination, before putting locks everwhere, was to rewrite it as an event-driven application using WaitForMultipleObjects. I can't remember now what that didn't work.
The other side - configuring the hardware - is my bread and butter, and there are a few simple abstractions that are pretty old now ( I have been using them since the late '80s ) that will help greatly.
Sadly, for inexplicable economic reason(s), these are less well known year by year.
Also - for extra points, think about how you'd do that in one thread. Betcha can... although multiprocessor can be pretty cool. Now write it to where it doesn't matter if it's one or multiple threads...