Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Thu, 02 May 2024 06:53:32 +0000
Post From: Bug in sc.BaseData during replay?
| [2019-11-18 14:51:03] |
| BrMa - Posts: 77 |
|
But just simply looking at what you said in post #3 why do you think there is a problem? It is perfectly normal for the sc.BaseData values to change at indexes from the old array size up to the current size during chart updating.
Because: First there is an increase to 11990 - the new high (11990) is established by the last tick (11990). So far so good. In the next iteration (-> the next tick!) the new high is 11992 giving a new last tick with 11991. BUT: where is the tick that brought the high to 11992 if the last one is 11991? How can there be a new high of the bar without a tick making the high? From an exchange point of view, this is impossible. There is a one to one-relation between a tick and a price. So the bar cannot make a new high (11992) and close at a different price (11991) with one tick, because either the price of the tick is 11992 OR 11991 - it cannot be both! Do you see my point? |