Experts: MQL5 Programming for Traders – Source Codes from the Book. Part 5

[Automated-Trading]

MQL5 Programming for Traders – Source Codes from the Book. Part 5:

In Part 5 of the book, we'll delve deeper into the APIs associated with algorithmic trading, including financial data analysis and processing, chart visualization, automation, and user interactions.

Author: MetaQuotes

[Peng Peng Liu]

Learn from the West.

[Zheng Yong Hong]

Thank you, sir.

[Vitaliy Belomestnov]

Automated-Trading:

MQL5 Programming for Traders - source codes from the book. Part 5:

Author: MetaQuotes

Where is the book? 🤔

[Ihor Herasko]

Vitaliy Belomestnov #:
Where's the book? 🤔

In the header of the page - Algotrading Tutorial.

[Stanislav Korotky]

I attach here a slightly modified version of the indicator IndDeltaVolume.mq5. In this version, the tester has disabled the output of warnings that the CopyTicksRange function did not return data. At the moment, the tester has a bug that the request of ticks on the history (even within visible bars) returns 0 and zero error code. A similar problem is demonstrated for the test indicator from MQ.

When working in the tester, CopyTicksRange returns ticks only for bars starting from the test date, which for this indicator means a delay on BarCount bars - further the histogram is drawn normally. There is no such problem on the online chart.

Also added delta calculation for real volumes (previously only buy and sell were displayed separately) and horizontal level 0.

[Aleksey Nikolayev]

I did not find examples of using the CopySeries() function in the book. Did I look badly or is there some reason not to use it?

[Stanislav Korotky]

Aleksey Nikolayev #:
I did not find examples of using the CopySeries() function in the book. Did I look badly or is there some reason not to use it?

You can consider it an omission, which happened because the function was added to the API when the book was already half-written (including the corresponding section). In many other cases, MQL5 updates were promptly added before finalisation, but not here. On the other hand, the book does not have to contain absolutely the entire API.

[Aleksey Nikolayev]

Stanislav Korotky #:

You can consider it an omission, which happened because the function was added to the API when the book was already half-written (including the relevant section). In many other cases, MQL5 updates were promptly added before finalisation, but not here. On the other hand, the book does not have to contain absolutely the entire API.

Not the slightest attempt to criticise, I just thought that suddenly something is wrong with this function (I didn't think about the dates of the book and the introduction of the function).