Errors, bugs, questions - page 861

[[Deleted]]

Yedelkin:
Yes, I agree, I didn't take into account the peculiarities you mentioned. And checking everything through MqlDateTime is somehow not elegant.

All right, I'll override it with acceleration.

[[Deleted]]

Who can say anything about the bug when the quotes are fully downloaded from the server and the left side of the chart is taken from the day candlesticks on the minute timeframes? That is, the M15 TF shows the day candles and then the M15 candles start at a certain point. Because my indicator is very sensitive to this fact.

Here are screenshots in different TFs

https://www.mql5.com/ru/charts/13869/eurusd-m1-metaquotes-software-corp

https://charts.mql5.com/1/26/eurusd-m15-metaquotes-software-corp-6.png

https://charts.mql5.com/1/26/eurusd-m30-metaquotes-software-corp-2.png

https://charts.mql5.com/1/26/eurusd-h1-metaquotes-software-corp-9.png

https://charts.mql5.com/1/26/eurusd-h4-metaquotes-software-corp.png

https://charts.mql5.com/1/26/eurusd-d1-metaquotes-software-corp-7.png

[Yedelkin]

FiftyStars: Who can say anything about the bug when the quotes are fully downloaded from the server and the left side of the chart is taken from the day candlesticks on the minute timeframes? That is, the M15 TF shows the day candles and then the M15 candles start at a certain point. Because my indicator is very sensitive to this fact.

The issue has already been raised several times. The explanation was as follows: the history of 1-minute timeframes, on the basis of which all other timeframes are built, is limited. Outside this M1 history there is a history consisting only of daily bars. Apparently, you have just discovered this boundary.

[[Deleted]]

Yedelkin:
The issue has already been raised several times. The explanation has been given as follows: the history of the minute timeframes, on the basis of which all other TFs are built, is limited. Outside this M1 history there is a history consisting only of daily bars. Apparently you are just discovering this boundary.

yes i understand, but geez, is there no way to limit this? apparently this is far from being a priority issue for the release of a patch on this issue

[Yedelkin]

FiftyStars: I understand, but, man, is there no way to limit it? Apparently it's far from a priority issue to release a patch on this

What do you mean "limit it"? Leave only the minute history?

[[Deleted]]

Yedelkin:
What do you mean by "restrict"? To leave only one-minute history?

The thing is that SeriesInfoInteger(Symbol(),Period(),SERIES_FIRSTDATE) on M15 takes these candlesticks as if they were native. The same goes for Bars(). Is there any way to programmatically detect candlesticks from a different TF?

[Yedelkin]

FiftyStars:

Yedelkin:
What do you mean by "limit"? To leave only the one-minute history?

The thing is, the SeriesInfoInteger(Symbol(),Period(),SERIES_FIRSTDATE) on M15 takes these candles as its own. The same thing with Bars(). is it possible to detect candles from another timeframe?

So, you want to leave only the one-minute history? The answer is not quite clear.

[[Deleted]]

Yedelkin:
So you're still suggesting we keep just the one-minute story? The answer is not quite clear.

I do not need D1 and W1 candlesticks on the 15-minute chart for the TF, in which there is no history, so that the graph ends rather than continues with the history of a larger TF.

[Yedelkin]

FiftyStars: I don't need D1 and W1 candlesticks on the 15 minute chart in TFs where there is no history to make the chart end and not continue with the history of the bigger TF.

I see. Of course, we can submit an offer to Service Desk to get an official response. But I'm afraid that the answer will be something like this: "The programmer can calculate the boundary date and limit the depth of the requested history...".

[Vladimir Gomonov]

Yedelkin:
.............. But I'm afraid the answer would be something like this: "the programmer is able to calculate the boundary date and limit the depth of the requested history"...

Better still, MetaQuotes programmers (i.e. the terminal) would recognize it.

The problem is really very stinking. And the dnafs have no right to sit on my 1-5-15-30M timeframe. They have no right to sit on my 1-5-15-30M timeframe.