Support Board
Date/Time: Mon, 25 Nov 2024 03:30:10 +0000
Post From: Significant Lag past version 1958
| [2019-07-31 09:27:22] |
| |
|
Here is another piece of information. Previously we were using the operating system timer functionality to drive charts but that is a low priority message. This is from the Microsoft documentation: The WM_TIMER message is a low-priority message. The GetMessage and PeekMessage functions post this message only when no other higher-priority messages are in the thread's message queue.
Now the charts are driven with a normal priority message that when received, is followed through on. Sierra Chart does not ignore these messages whereas with OS timer messages they are low priority and when there was more than one of them in the queue for a particular chart, they were all discarded and only one of them followed. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |