Well, in theory, if additional indicator buffers are self-declared and further trend lines are used, then it will work...
Then why does the documentation say that
the number of buffers cannot exceed 8
It's not clear here. It doesn't say it's the number of main buffers, not all of them. It says the number of buffers and that's it. So I'm reading this and it's my understanding that this should apply to the total number of buffers for a given indicator.
No, I'm talking about ObjectCreate(), you have to set the window number there. I showed you how to set it if it is a subwindow (i.e. not zero, which is the main window).
So you have the function parameter WindowOnDropped there when creating an object, and it's already sort of the main window relatively. Or is main window the leftmostwindow in the terminal?
This is where it is unclear. It doesn't say the number of main buffers... not all buffers. It says the number of buffers and that's it. So I'm reading it and it's supposed to apply to the total number of buffers of a given indicator.
I'm not talking about the indicator buffers, I'm talking about the simulated indicator buffers. There ArrayResize(CustomBuffer, Bars) in the wrapper from IndicatorCounted(), and the ends of the rightmost trend lines should be redrawn by bid.
hoz:
So you have a function parameter there when creating an object - WindowOnDropped, and it's already sort of the main window relatively. Or is the main window leftmostamong windows in the terminal?
No, I was confused at first, too. For example, we have two charts open, euron and gold. So, they both have an index of zero. But if they have sub-windows, they are numbered from one. For example, I have thrown three indices on the eurenne chart, two on gold, and all five with #property separate_window and all different subwindows. Then eurene will have window numbers 0, 1, 2, 3 and gold 0, 1, 2.
I have a question. My brain is boiling, honestly. If you can - help me.
int n=1, limit=3;
double result;//или int result, что не столь сейчас важноdouble temp[];
int start(){
for(int slow=10; slow<=10*limit; slow++){
for(int fast=10; fast<=slow; fast++){
for(int period=1; period<=slow/10; period++){
n++; Print(n-1, ": ", slow-9, ", ", fast-9, ", ", period);
//здесь идёт тестирование машки с параметрами slow, fast, period, а результаты тестирования заносим в массив:ArrayResize(temp,n); temp[n-1]=result;
}
}
}
//и находим максимальный результат:int max=ArrayMaximum(temp);
return(0);
}
Now a question: how can I restore values slow, fast, period by max (which is position of an item in the array)? The order in which values are put in temp[] is given in Print(). I put 3 in limit, but any number can be used there. Here are the first 77 values (limit=2):
I have a question. My brain is boiling, honestly. If you can - help me.
Now a question: how can I restore values slow, fast, period by max (which is position of an item in the array)? The order in which values are put in temp[] is given in Print(). I put 3 in limit, but it can be any number.
Where "n++" check if result is maximal, if it is maximal, remember values of slow, fast, etc.
You could make three more arrays (or one three-dimensional array) for slow, fast... This is better, because in case you want to sort the results somehow, there will always be test parameters available.
If these actions are frequent, e.g. once per bar or 10 bars, it is better to scale arrays for results and three arrays with parameter values in the initem, scroll through these loops, fill the arrays with period values. Then scroll it all in one loop. Then we will be able to use the ArrayMaximum function, and sort things out. This will make the work as fast as possible.
No, I was confused at first too. For example, we have two charts open, the euro and gold. So, they both have an index of zero. But if they have sub-windows, they are numbered from one. For example, I have thrown three indices on the eurenne chart, two on gold, and all five with #property separate_window and all different subwindows. Then the eurene would have window numbers 0, 1, 2, 3 and gold would have 0, 1, 2.
Exactly! I just don't work with turkeys at all, so I didn't pay attention when I was studying the help. It all makes sense.
gyfto:
I am not talking about indicator buffers, I am talking about simulated indicator buffers. There ArrayResize(CustomBuffer, Bars) in the wrapper from IndicatorCounted(), and the ends of rightmost trend lines should be redrawn by Bid.
And I was asking specifically how to draw more than 6 lines on a graph. In which window (0 or other, it doesn't matter). This is what I'm most interested in right now and that's what I asked originally.
Where "n++" make check for maximal result, if maximal, remember values of slow, fast, etc.
Didn't think about it.
Integer: You can make three more arrays (or one three-dimensional array) for slow, fast... That's better, because in case you want to sort the results somehow, there will always be test parameters available.
Three-dimensional is ideal, but ArrayMaximum() only works on one-dimensional, so you'll have to converge the array into a linear one, and again you'll have to figure out where everything is. But I have fastMax=slow, and that's the trouble. But three different arrays... I have the same result, so it's either one three-dimensional or one linear.
Integer: scale arrays for results
I don't know this terminology, please explain. Create a linear array of length in a cube?
Well, at least there's an option already. Via MathMax(result, resultPrev).
Well, in theory, if additional indicator buffers are self-declared and further trend lines are used, then it will work...
Then why does the documentation say that
No, I'm talking about ObjectCreate(), you have to set the window number there. I showed you how to set it if it is a subwindow (i.e. not zero, which is the main window).
So you have the function parameter WindowOnDropped there when creating an object, and it's already sort of the main window relatively. Or is main window the leftmostwindow in the terminal?
Hello! I can't understand why buystop orders are not deleted.
Then why does the documentation say that
I'm not talking about the indicator buffers, I'm talking about the simulated indicator buffers. There ArrayResize(CustomBuffer, Bars) in the wrapper from IndicatorCounted(), and the ends of the rightmost trend lines should be redrawn by bid.
So you have a function parameter there when creating an object - WindowOnDropped, and it's already sort of the main window relatively. Or is the main window leftmostamong windows in the terminal?
I have a question. My brain is boiling, honestly. If you can - help me.
Now a question: how can I restore values slow, fast, period by max (which is position of an item in the array)? The order in which values are put in temp[] is given in Print(). I put 3 in limit, but any number can be used there. Here are the first 77 values (limit=2):
I have a question. My brain is boiling, honestly. If you can - help me.
Now a question: how can I restore values slow, fast, period by max (which is position of an item in the array)? The order in which values are put in temp[] is given in Print(). I put 3 in limit, but it can be any number.
Where "n++" check if result is maximal, if it is maximal, remember values of slow, fast, etc.
No, I was confused at first too. For example, we have two charts open, the euro and gold. So, they both have an index of zero. But if they have sub-windows, they are numbered from one. For example, I have thrown three indices on the eurenne chart, two on gold, and all five with #property separate_window and all different subwindows. Then the eurene would have window numbers 0, 1, 2, 3 and gold would have 0, 1, 2.
Exactly! I just don't work with turkeys at all, so I didn't pay attention when I was studying the help. It all makes sense.
I am not talking about indicator buffers, I am talking about simulated indicator buffers. There ArrayResize(CustomBuffer, Bars) in the wrapper from IndicatorCounted(), and the ends of rightmost trend lines should be redrawn by Bid.
Where "n++" make check for maximal result, if maximal, remember values of slow, fast, etc.
Didn't think about it.
You can make three more arrays (or one three-dimensional array) for slow, fast... That's better, because in case you want to sort the results somehow, there will always be test parameters available.
Three-dimensional is ideal, but ArrayMaximum() only works on one-dimensional, so you'll have to converge the array into a linear one, and again you'll have to figure out where everything is. But I have fastMax=slow, and that's the trouble. But three different arrays... I have the same result, so it's either one three-dimensional or one linear.
scale arrays for results
I don't know this terminology, please explain. Create a linear array of length in a cube?
Well, at least there's an option already. Via MathMax(result, resultPrev).