Hello, Can you please tell me if you need to type in iData for this indicator, no matter if it's any program or reference to the bar data, where you can specify the timeframe, why is the data from other timeframes are not reflected correctly in the current different on timeframe chart, but only in the chart of the specified timeframe? Thank you.
Функции для работы с таймсериями и индикаторами. Таймсерия отличается от обычного массива тем, что индексация элементов таймсерии производится от конца массива к началу (от самых свежих данных к самым старым). Для копирования значений таймсерий и индикаторов рекомендуется использовать только динамические массивы, так как функции копирования...
Thanks for the link, I have exactly the same picture, only a slightly different algorithm, the point is to make more points (in the final drawing), make them appear with a threshold.
Thanks, I will definitely look into it, but as an example the principle why does it not work if instead of writing the data of another timeframe instead of zero, why is it not reflected correctly, should I copy it first and then render it ?
Thanks for the link, I have exactly the same picture, only a slightly different algorithm, the essence is to make more points (in the final drawing), to make them appear with a threshold.
You can do so, but it turns out Renco, ie divides into equal segments distance m / a vertex. This breaks the algorithm itself search vertices, the question how to make while maintaining the initial code, the threshold between points (on additionally drawing), should get a multiple of the distance between all but the last and the top (will be less than the threshold).
Thank you, I will look into it, but as an example why does it not work if instead of writing zero you put in data of another timeframe, why is it not reflected correctly, should I copy it first and then draw it?
CopyClose is a more modern function, but ok,iClose(...) works fine
How does it not work correctly? A picture or a piece of code, please be more specific.
CopyClose is a more modern function, but okay, iClose(...) works fine
How does it work incorrectly? A picture or a piece of code, please be more precise.
Well, here is a simple example, I want to see close prices on the chart, I want to see one hour on the timeframe, everything is good on the clock, but it's different on any other timeframe. The idea was to see the closing prices of the higher ones on a smaller timeframe. The picture is 30 min.
PokrovMT5: Well here is the simplest example, I want to see the closing prices on the chart, the timeframe is written one hour, everything is good on the clock, everything is different on any other timeframe. The idea was to see the closing prices of the higher ones on a smaller timeframe. The picture is 30 min.
Like this
int shift;
datetime T;
for(i=limit; i>=0; i--)
{
T = iTime(NULL,0,i);
shift=iBarShift(NULL,60,T);
C=iClose(NULL,60,shift);
CC[i]=C;
}
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
Hello, Can you please tell me if you need to type in iData for this indicator, no matter if it's any program or reference to the bar data, where you can specify the timeframe, why is the data from other timeframes are not reflected correctly in the current different on timeframe chart, but only in the chart of the specified timeframe? Thank you.
I don't quite understand
But I think this will help
Thanks for the link, I have exactly the same picture, only a slightly different algorithm, the point is to make more points (in the final drawing), make them appear with a threshold.
I don't quite get it.
But I think it helps.
Thanks, I will definitely look into it, but as an example the principle why does it not work if instead of writing the data of another timeframe instead of zero, why is it not reflected correctly, should I copy it first and then render it ?
Check it out here.
Thanks for the link, I have exactly the same picture, only a slightly different algorithm, the essence is to make more points (in the final drawing), to make them appear with a threshold.
You can do so, but it turns out Renco, ie divides into equal segments distance m / a vertex. This breaks the algorithm itself search vertices, the question how to make while maintaining the initial code, the threshold between points (on additionally drawing), should get a multiple of the distance between all but the last and the top (will be less than the threshold).
For some reason the code didn't insert the comment immediately, I had to rewrite it.
Thank you, I will look into it, but as an example why does it not work if instead of writing zero you put in data of another timeframe, why is it not reflected correctly, should I copy it first and then draw it?
CopyClose is a more modern function, but ok,iClose(...) works fine
How does it not work correctly? A picture or a piece of code, please be more specific.
CopyClose is a more modern function, but okay, iClose(...) works fine
How does it work incorrectly? A picture or a piece of code, please be more precise.
Well here is the simplest example, I want to see the closing prices on the chart, the timeframe is written one hour, everything is good on the clock, everything is different on any other timeframe. The idea was to see the closing prices of the higher ones on a smaller timeframe. The picture is 30 min.
Like this
That's the way it is.
Thank you very much!