After doing a little more investigation, I found out the number of threads
has nothing to do with the timing problem (evidently, CVI and/or Windows
spawns threads in the background, depending on what a user is doing in the
GUI).
The issue is this: When I run my app from CVI, it works fine but if I run
that same debug version of the executable with Windows Explorer, the timing
is erratic. However, if I exit the CVI IDE before running my app from
Explorer, then the executable works fine!
Does the CVI runtime engine that the executable depends on behave
differently somehow when the CVI IDE is active? And when the IDE is active,
why would the executable work fine when launced by it but run erratically
when launched by Explorer?
PG