You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Dear developers!
I REQUIRE YOU to read this message attentively.
I think I've figured out the reason why the time discrepancy appears!!!
Today:
Terminal
Expert
Time check mechanism.
When the Depth of Market changes for a symbol(I work with the Depth of Market only)
TheCheckMarketTime function is called
After getting the data on the latest tick for the symbol
I check for the timeframe, but(VERY IMPORTANT) !!!!
MqlTick (IMMEDIATELY) does not contain the latest timeframe, if
in the Depth of Market has changed ONLY the volume of the same price.
I am making this assumption because there is no
TICK_FLAG_ASK_VOLUMEand TICK_FLAG_BID_VOLUME flags
The OnBookEvent function worked (volume of such and such price has changed), but
MqlTick did not register time of this change.
Please add these flags to MqlTick, respectively with updated time.
Added
For some reason I can't make a record in the CD
MqlTick (RIGHT HERE) does not record the latest time if
in the price cup ONLY the volume of the same price has changed.
Absolutely correct. And this is correct behaviour. MqlTick takes data from the same source from which the tick history is filled. There shouldn't be duplicates in tick history, because the tick history in MT5 doesn't store volume even on bestbands.
It's been raised for a long time that there is no direct way to know the time to which the tick history corresponds. Find out in another way.
Absolutely right. And this is the correct behaviour. MqlTick takes data from the same source from which the tick history is filled. There should not be duplicates in tick history, because the tick history in MT5 does not store volume even on bestbands.
It's been raised for a long time that there is no direct way to know the time to which the tick history corresponds. Find out in another way.
Would you be so kind as to suggest which one?
Added
If I got a notification that something had changed in the takan, then
why not add a field for convenience ("little blood")
datetime book_change; ?
Or even simpler, add the following field to MqlBookInfo
datetime book_change;
Especially as this time is translated by exchange.
Would you be so kind as to tell me which one?
Don't be ridiculous... :)
If I have been notified that something has changed in takan, then
why not add a field for convenient ("little money")
datetime book_change; ?
Or simply, add MqlBookInfo structure with the
datetime book_change;
Especially, that this time is translated by the exchanger.
Only not datetime, but long - milliseconds. And
Forum on trading, automated trading systems and strategy testing
Market closed
fxsaber, 2017.09.22 09:17
The issue has been raised for a long time that there is no direct way to know the time to which the betting window corresponds.
With similar suggestions.
Maybe after the OnBookEvent is triggered
request CopyTicks on this character?
I'll give it a try...
Maybe after the OnBookEvent is triggered
request CopyTicks on this character?
Wouldn't help, of course. The only option now is to find out the timing of the tumbler led.
It won't help, of course. The only option now is to find out the timing of the glass led.
It's interesting :)
Result
???????
I don't even know what to say....
I don't even know what to say....
you will see that the timing will only be different in these situations
It has been discussed several times that MqlTick does not return a tick as is. That there are two tick streams - quote and transaction. And that in CopyTicks they are merged sometimes retroactively, because the streams are unsynchronized. And that times of MqlTick and CopyTicks may not coincide.