LabVIEW
Architecture question
@jfalesi wrote:
I was mainly wondering if it's worth creating messages and states when the only real issue I'm having with the current architecture is race conditions b/c we're using local vars and property nodes to handle shutdown.
That depends on who you ask. I'd lean towards 'no', but then I know all the tricks and caveats well enough to do it myself.
10 ms latency is typically something that you cannot guarantee on a Windows machine. More like 200 ms if the loop can be tight, but then you might still not make that in certain situations (virus scanning, backups, updates, etc.).
Search LabVIEW like a graph! 
I think you should always strive for perfection even though you'll likely end up with "good enough". Your "good enough" will then be better than someone else's "good enough", if they started out aiming for "good enough" to begin with.
@billko wrote:
I think you should always strive for perfection even though you'll likely end up with "good enough". Your "good enough" will then be better than someone else's "good enough", if they started out aiming for "good enough" to begin with.
My 'good enough' is perfection to most.
(couldn't resist, not how I really feel. At least not all the time 
).
