Thx for the warning, Janus.
I read you whole thread with this 'repeated first bar' issue when iog is on....
The real-time features of either MC and WINDOWS are effectively quite questionable ...
It reminds me of a currently pending issue that I once raised here :
http://forum.tssupport.com/viewtopic.ph ... ght=update
and that has still not been fully answered.
When a slower timeframe (say data2 : 5mn) is referenced in a strat that applies to a 1mn chart (data1), then the slower timeframe (5mn) is not updating correctly ...
data2 updating correctly on each tick of data1 at 18H45
1100310-1845 - close data1(1mn): 1.36360 - close data2(5mn): 1.36360
1100310-1845 - close data1(1mn): 1.36358 - close data2(5mn): 1.36358
1100310-1845 - close data1(1mn): 1.36358 - close data2(5mn): 1.36358
1100310-1845 - close data1(1mn): 1.36357 - close data2(5mn): 1.36357
1100310-1845 - close data1(1mn): 1.36357 - close data2(5mn): 1.36357
data2 NOT updating correctly on each tick of data1 at 18H46, or 18H49
1100310-1846 - close data1(1mn): 1.36353 - close data2(5mn): 1.36354
1100310-1846 - close data1(1mn): 1.36352 - close data2(5mn): 1.36354
...
1100310-1849 - close data1(1mn): 1.36397 - close data2(5mn): 1.36354
1100310-1849 - close data1(1mn): 1.36397 - close data2(5mn): 1.36354
1100310-1849 - close data1(1mn): 1.36399 - close data2(5mn): 1.36354
then data2 will update correctly again at 18H50 ... !!!
then data2 will be stuck again at 18H52 ... or 18H53 ...
I don't know if this issue relates to the one you raised with the 'repeated first bar' ... but it definitely is a real-time problem for intrabar-oriented code.
TSS is aware of that point and is supposed to work on it in a next version, but maybe you have an idea ... ?