Discussion of article "Library for easy and quick development of MetaTrader programs (part XXIV): Base trading class - auto correction of invalid parameters"

New comment
 

New article Library for easy and quick development of MetaTrader programs (part XXIV): Base trading class - auto correction of invalid parameters has been published:

In this article, we will have a look at the handler of invalid trading order parameters and improve the trading event class. Now all trading events (both single ones and the ones occurred simultaneously within one tick) will be defined in programs correctly.

Generally, the EA should be able to act according to the circumstances while following the user-defined logic of handling errors in trading orders. Thus, we may give the following instructions to the EA when a trading order error is detected:

  1. Simply exit the trading method letting the user create the handler of invalid parameters of an erroneous order on their own.
  2. If an invalid value of a trading order can be fixed, do that right away and send it to the server,
  3. If a situation and an error are appropriate, repeat a trading request after a pause or simply repeat the request with the same parameters.

Handling errors in trading order parameters may lead to one of several outcomes:

  • Inability to continue trading using the EA before an error source is eliminated by the user.
  • Inability to send a trading order — exit from the trading method.
  • Correcting invalid values and sending a fixed trading order.
  • Immediate sending of a trading order with the initial parameters (here the assumption is made that trading conditions have improved).
  • Waiting, updating quote data and sending a trading order with the initial parameters.

In this article, we are going to develop the trading order error handler that will check errors and their sources, as well as return the error handling method:

  • disabling trading operations,
  • interrupting a trading operation,
  • correcting invalid parameters,
  • trading request with initial parameters,
  • trading request after waiting (temporary solution),
  • creating a pending trading request (in subsequent articles)

Author: Artyom Trishkin

 
Can you tell me how to get information about a losing order? Such as the amount of loss, order number, order quantity, opening time, etc.. Thank you!
 
hsyhsy863 :
Can you tell me how to get information about a losing order? Such as the amount of loss, order number, order quantity, opening time, etc.. Thank you!
Here you can ask your questions.
 
Artyom Trishkin:
Here you can ask your questions.
My question is, when designing an automated trading programme using your program, I need to close a losing order, how can I get the order number of the losing order?
 
hsyhsy863 :
My question is when designing an automated trading programme using your program, I need to close a losing order, how do I get the order number of the losing order?

In the adviser. 

//--- Get a list of all open positions
   CArrayObj* list=engine.GetListMarketPosition();
//--- Sort the list by profit, taking into the commission and swap
   list.Sort(SORT_BY_ORDER_PROFIT_FULL);
//--- Get the index of the position with the lowest profit (largest loss)
   int index=CSelect::FindOrderMin(list,ORDER_PROP_PROFIT_FULL);
   if(index>WRONG_VALUE)
     {
      //--- Get the position object with the largest loss and close the position by ticket
      COrder* position=list.At(index);
      if(position!=NULL)
         engine.ClosePosition(position.Ticket());
     }

The library should be connected in accordance with the expert example attached to this article.

 
Artyom Trishkin:

In the adviser.

The library should be connected in accordance with the expert example attached to this article.

The library should be connected in accordance with the expert example attached to this article!
 
Hello, when I was designing the auto-trading, I found that when OP_BUYSTOP and OP_SELLSTOP are placed at the same time, only OP_SELLSTOP is placed but not OP_BUYSTOP. The statement fully meets the conditions of the pending order but it can't be pending.
 
hsyhsy863 :
Hello, when I was designing the auto-trading, I found that when OP_BUYSTOP and OP_SELLSTOP are placed at the same time, only OP_SELLSTOP is placed but not OP_BUYSTOP. The statement fully meets the conditions for pending orders, but the orders cannot be pending.
Provide an example to reproduce this error.
 
Artyom Trishkin:
Provide an example to reproduce this error.
if(datetimeN5!=iTime(NULL,0,0))
if(datetimeN5!=iTime(NULL,0,0))
if(ASWER(Close Position, "Upper Pending Bid")==0) { if(datetimeN5!=iTime(NULL,0,0))
{
Pending Buy(0.382,Closed); {
datetimeN5 = iTime(NULL, 0, 0);
}}
if(datetimeN6!=iTime(NULL,0,0))
{
if(ASWER(Close Position, "Down Pending Sell Count") == 0)
{
Pending Sell(0.382,Close Position);
datetimeN6 = iTime(NULL, 0, 0);

}}

This is the source code for my pending buy and pending sell, there should logically be two pending orders at the same time, but in reality there is only the pending sell order.

 
Sorry, problem solved, my mistake!!!!
 
hsyhsy863:
Sorry, problem solved, my mistake!!!!
OK
123
New comment