Features of the mql5 language, subtleties and tricks - page 125
![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Thank you!
And this is an older code, but in pictures:TrailingStop
EventSetTimer in OnInit in Tester counts down not from beginning of day of first tick, but from initial date of testing interval - balance transaction.
Forum on trading, automated trading systems and trading strategies testing
Features of mql4 language, tips and tricks
fxsaber, 2019.02.12 13:12
Features of ArrayResize for multidimensional arraysHow nice it would be to see Kim's functions for the five. Can you give me a hint, please? There was a function like this in Kim's
I am trying to rewrite it on mql5. But it does not want to work. How to force it? :)
How nice it would be to see Kim's functions for the five. Can you give me a hint, please? There was a function like this in Kim's
I am trying to rewrite it on mql5. But it does not want to work. How to force it? :)
Forum on trading, automated trading systems and strategy tester
Libraries: MT4Orders
fxsaber, 2019.01.13 17:23
Kim's features under MT4 are quite popular, so downloaded all the sources from his site and wrote a simple "converter" for them under MT5.Thanks for the crutch, very good :) But I'm learning a fiver for understanding, getting into it, so it's important to handle it by hand, fundamentally sorting out the knuckles.
While parsing millions of ticks, I decided to periodically look at memory consumption.
I noticed that after making changes the execution speed has dropped many times.
Reason: some variants of TerminalInfoInteger use take very long time to execute
Be careful.A very expensive function.
Also TERMINAL_MEMORY_AVAILABLE
TERMINAL_MEMORY_PHYSICAL and TERMINAL_MEMORY_TOTAL are cached after the first request. Subsequent queries will return the cached values