Features of the mql5 language, subtleties and tricks - page 37
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
HistorySelect is a very expensive function. But HistorySelectByPosition is even more expensive.
For example, if you need to find the first deal of the closed position, you can act in two ways
The second item could be much cheaper. But certainly not more expensive.
Calling HistorySelect*-functions in the tester is almost a waste of computing resources. Therefore you should always try to minimize their number. Especially HistorySelectByPosition.
For Hedge accounts in the testerThis means that the tester result depends very much on the type of account.
As it turned out in one of the neighboring threads, the tester result even depends on whether the testing is done on a local agent or on one of the distributed network agents.
https://www.mql5.com/ru/forum/1111/page1880#comment_4904481
As it turned out in one of the neighboring threads, the result of the tester even depends on whether the testing takes place on a local agent or on one of the agents of a distributed network.
https://www.mql5.com/ru/forum/1111/page1880#comment_4904481
You described BAG, which is not in the context of this thread. The difference in the execution of limiters is the official position.
I agree, I just wanted to note that the tester is becoming more and more unpredictable tool.
I agree, I just wanted to note that the tester is becoming an increasingly unpredictable tool.
This means that the result of the tester depends very much on the type of account.
Result
Forum on trading, automated trading systems and trading strategies testing
Bugs, bugs, questions
fxsaber, 2017.04.10 16:53
Dear developers, how to get rid of Warnings in this situation?Rudiment functions (not needed)