Tweet
While executing a FOR or WHILE loop, it would be great to be able to include an "application.ProcessMessages();" function to allow windows and other apps to continue to process recent data/ticks.
I've noticed that running esignal with a looping feature to execute scheduled events, LOCKS the cpu and all other apps from processing new ticks.
When the loop completes, esignal then processes the pending ticks as they've been held up by the looping call.
If you added a simple call to the Windows function to "Process Messages", this should resolve this problem. It should continue looping as well call other windows events, thus resolving the issue of the LOCK.
Hope this helps and can be done easily.
I've noticed that running esignal with a looping feature to execute scheduled events, LOCKS the cpu and all other apps from processing new ticks.
When the loop completes, esignal then processes the pending ticks as they've been held up by the looping call.
If you added a simple call to the Windows function to "Process Messages", this should resolve this problem. It should continue looping as well call other windows events, thus resolving the issue of the LOCK.
Hope this helps and can be done easily.