Discussion of article "Library for easy and quick development of MetaTrader programs (part II). Collection of historical orders and deals" - page 3

 
Artyom Trishkin:

What version of library are you using?

What version of test adviser are you using?

Hello Artyom, thanks for your reply.

In the first step, I had copied the program from the forum here.

I did not have compilation errors until then.

In the next step, I have used the file which is attached here, but it has produced the same error.

Is there another place where I can find an "up to date" version?

thanks in advance, and your work and help here is highly appreciated!


 
KjLNi :

Hello Artyom, thanks for your reply.

In the first step, I had copied the program from the forum here.

I did not have compilation errors until then.

In the next step, I have used the file which is attached here, but it has produced the same error.

Is there another place where I can find an "up to date" version?

thanks in advance, and your work and help here is highly appreciated!


1. Delete the entire folder from the data location of your terminal MQL5\Include\DoEasy\ (delete only DoEasy - Do not delete Include!)

2. Copy the DoEasy folder from the zip files attached to this article to Include\. This guarantees you version 2 of the library for the test advisor, which is in the files of this article.

3. Use the Expert Advisor file located in the zip-files attached to this article for testing - from the Experts\TestDoEasy\Part2\ location

The latest version of the library is here (russian):

Библиотека для простого и быстрого создания программ для MetaTrader (Часть XXXI): Отложенные торговые запросы - открытие позиций по условиям
Библиотека для простого и быстрого создания программ для MetaTrader (Часть XXXI): Отложенные торговые запросы - открытие позиций по условиям
  • www.mql5.com
При проектировании функционала библиотеки была запланирована концепция торговли при помощи отложенных запросов, в которую входят два варианта работы — обработка ошибок торгового сервера и обычная отсылка торговых приказов по программно заданным условиям.  В предыдущих статьях, начиная со статьи 26, мы шаг за шагом создали обработку ошибок...
 
Are you work for metaquote? Why the standard mqh file in mt5 are similar but not the same as yours?
 
Xiaowei Yan :
Are you work for metaquote? Why the standard mqh file in mt5 are similar but not the same as yours?

1. No. 2.

2. What file are you talking about?

 

This is a great idea! Thank you very much for the provided material.

I didn't download the attached files on purpose. As I studied the article, I decided to type everything with my own hands. It is easier to understand and memorise, and it is useful for practice.

And actually I found a small mark in this article. It does not say anywhere that in HistoryCollection.mqh in lines 14,15,16 should be connected HistoryOrder.mqh, HistoryPending. mqh and HistoryDeal .mqh.

For me, as a beginner, I had to strain my brain a lot. =))

 
Aleksandr Brown:

This is a great idea! Thank you very much for providing the material.

I didn't download the attached files on purpose. As I studied the article, I decided to type everything with my own hands. It is easier to understand and memorise, and it is useful for practice.

And actually I found a small mark in this article. It does not say anywhere that HistoryOrder .mqh, HistoryPending .mqh and HistoryDeal .mqh should be connected in HistoryCollection . mqh in lines 14,15,16.

For me, as a beginner, I had to strain my brain a lot. =))

Thank you.

Well you see, sometimes "mistakes" make you think and find solutions ;).

At the initial stage, in the articles everything is "chewed up". But the further you go, the less detailed everything is described with the aim that a person carefully read the first articles and further on will understand everything himself about library constructions.

 

Very interesting work. I am studying it line by line. I try to rewrite the code manually, and I encountered an error in the string function COrder::StateDescription(void).

The compiler was swearing at StateOrder(). I found the solution in the archive files, and there is a lot of other things there. But it's even good for warming up my brain :)

 
Ildar Valiullin #:

Very interesting work. I am studying it line by line. I try to rewrite the code manually, and encountered an error in the function string COrder::StateDescription(void).

The compiler was swearing at StateOrder(). I found the solution in the archive files, and there is a lot of other things there. But it's even good for warming up my brain :)

I'm glad you managed to find a solution yourself.