Question, is it possible to call a standard indicator in a custom indicator, but for a standard indicator to be calculated based on another custom indicator instead of the price?
Pyxlik2009>>: парни кто обьяснит Pyxlik2009 писал(а)>>
Все слава богу написал но вот сталкнулся с такой проблемой тестится тестится а потом тупо встанет и стоит в чем проблема?
и можно как нибудь увеличить скорость тестирования а то у меня не один так советник долго не тестится )))
If you optimize on a large timeframe - H4 or D1, using the method of all ticks and on a long timeframe, it happens. It is necessary to optimize the code, remove all unnecessary loops, reduce the size of buffers, arrays (where it is not necessary). Better yet, write the Expert Advisor for the opening prices. Make sure there is enough free memory left. In the past there were very strange bugs, for example, abundant use of comments like [/* ... */] slowed down testing, and after they were removed the testing started to run.
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.
Question, is it possible to call a standard indicator in a custom indicator, but for a standard indicator to be calculated based on another custom indicator instead of the price?
Thank you.
Unless, of course, it is "OnArray".
Что в коде стандартного заложено, на основе того он и будет расчитываться. Т.е. нельзя.
Если конечно не "OnArray"
What does it look like in the code?
You fill an array and then put a "standard indicator" on it (RSIOnArray, CCIOnArray etc. - about 7 pieces).
Latest mention on the forum , and in general F1, tutorial etc.
Все слава богу написал но вот сталкнулся с такой проблемой тестится тестится а потом тупо встанет и стоит в чем проблема?
I need a bit more speed to test the system, but my EA is not tested for a long time )))
парни кто обьяснит Pyxlik2009 писал(а) >>
Все слава богу написал но вот сталкнулся с такой проблемой тестится тестится а потом тупо встанет и стоит в чем проблема?
и можно как нибудь увеличить скорость тестирования а то у меня не один так советник долго не тестится )))
If you optimize on a large timeframe - H4 or D1, using the method of all ticks and on a long timeframe, it happens. It is necessary to optimize the code, remove all unnecessary loops, reduce the size of buffers, arrays (where it is not necessary). Better yet, write the Expert Advisor for the opening prices. Make sure there is enough free memory left. In the past there were very strange bugs, for example, abundant use of comments like [/* ... */] slowed down testing, and after they were removed the testing started to run.
Here's the code for a newbie, please.
вот код подскажите новичку плиз.