Does anybody knows what happens in the CVI RTE when you call the WIN32 SDK
function SetTimer and start the LW RTE with RunUserInterface. We have
In our application we use the SDK function SetTimer to create a timer with
an intervall of 10ms. Even if the Timer callback function is empty the CPU
usage climbs up to about 55% when starting the CVI user interface. Other
processes and threads have about 40% longer runtimes as before starting the
user interface.
For testing we wrote the following short code.
........
SetSleepPolicy (VAL_SLEEP_MORE);
TimeIdent=SetTimer(NULL,0,10,TimerProc);
RunUserInterface ();
......
Has anybody experienced a similar problem.
IVM Automotive
Michael Koch & Stefan Urich
