What's new in MetaTrader 5

The history of updates of the desktop, mobile and web platforms

12 May 2016
MetaTrader 5 Web Platform: Now available for beta testing

The beta version of the MetaTrader 5 Web Platform has been released. The new product combines convenience and cross-platform nature of the web terminal with the advantages of the desktop version of MetaTrader 5 – speed, support for multiple markets, and expanded trading functions.

The MetaTrader 5 web platform is available on the MQL5.community, and it allows traders to perform trading operation on financial markets from any browser and any operating system, including Windows, Mac, and Linux. You only need to have an Internet connection. No additional software is required.

The following features are available in the beta version:

  • Hedging system
  • 30 technical indicators
  • 23 analytical objects
  • Full set of MetaTrader 5 trading orders
  • Interface in 41 languages
The release of the beta version aims to provide global public testing and to allow traders to evaluate the new capabilities.
22 April 2016
MetaTrader 5 build 1325: Hedging option and testing on real ticks

Terminal

  1. We have added the second accounting system — hedging, which expands the possibilities of retail Forex traders. Now, it is possible to have multiple positions per symbol, including oppositely directed ones. This paves the way to implementing trading strategies based on the so-called "locking" — if the price moves against a trader, they can open a position in the opposite direction.

    Since the new system is similar to the one used in MetaTrader 4, it will be familiar to traders. At the same time, traders will be able to enjoy all the advantages of the fifth platform version — filling orders using multiple deals (including partial fills), multicurrency and multithreaded tester with support for MQL5 Cloud Network, and much more.

    Now, you can use one account to trade the markets that adhere to the netting system and allow having only one position per instrument, and use another account in the same platform to trade Forex and apply hedging.

    Opening a hedge account and viewing position accounting type
    A position accounting system is set at an account level and displayed in the terminal window header and the Journal:



    To open a demo account with hedging, enable the appropriate option:




    Netting system
    With this system, you can have only one common position for a symbol at the same time:

    • If there is an open position for a symbol, executing a deal in the same direction increases the volume of this position.
    • If a deal is executed in the opposite direction, the volume of the existing position can be decreased, the position can be closed (when the deal volume is equal to the position volume) or reversed (if the volume of the opposite deal is greater than the current position).

    It does not matter, what has caused the opposite deal — an executed market order or a triggered pending order.

    The below example shows execution of two EURUSD Buy deals 0.5 lots each:


    Execution of both deals resulted in one common position of 1 lot.

    Hedging system
    With this system, you can have multiple open positions of one and the same symbol, including opposite position.

    If you have an open position for a symbol, and execute a new deal (or a pending order triggers), a new position is additionally opened. Your current position does not change.

    The below example shows execution of two EURUSD Buy deals 0.5 lots each:


    Execution of these deals resulted in opening two separate positions.

    New trade operation type - Close By
    The new trade operation type has been added for hedging accounts — closing a position by an opposite one. This operation allows closing two oppositely directed positions at a single symbol. If the opposite positions have different numbers of lots, only one order of the two remains open. Its volume will be equal to the difference of lots of the closed positions, while the position direction and open price will match (by volume) the greater of the closed positions.

    Compared with a single closure of the two positions, the closing by an opposite position allows traders to save one spread:

    • In case of a single closing, traders have to pay a spread twice: when closing a buy position at a lower price (Bid) and closing a sell position at a higher one (Ask).
    • When using an opposite position, an open price of the second position is used to close the first one, while an open price of the first position is used to close the second one.


    In the latter case, a "close by" order is placed. Tickets of closed positions are specified in its comment. A pair of opposite positions is closed by two "out by" deals. Total profit/loss resulting from closing the both positions is specified only in one deal.


  2. In addition to hedging support, the new platform version provides wider opportunities for migrating accounts from MetaTrader 4. Now, brokers can automatically transfer accounts to MetaTrader 5, including all operations: open and pending orders, and complete trading history.

    A welcome dialog appears when first connecting to the account migrated from MetaTrader 4. Data transmission is securely encrypted during migration. To get started, specify the password of your account that you used in MetaTrader 4, and then set a new password.



    Once connected, you will be able to continue using your account, just as if it has been opened in MetaTrader 5. The complete history of all trades from MetaTrader 4 is automatically added to the new account.

    The tickets of orders and positions (including history orders) are not preserved during import, because one history record from MetaTrader 4 can be imported as up to 4 history operations in MetaTrader 5. New tickets are assigned to all trading records.

    The account numbers can be preserved or replaced depending on how the broker imports them.

  3. Added the Chat. Now, you can communicate with your MQL5.community friends and colleagues. The chat displays all personal messages from your MQL5 account. To start communicating, log in to your account directly from the chat window or via the platform settings: Tools -> Options -> Community.




  4. Simplified demo account creation dialog, added ability to create hedge accounts. You do not have to fill the large form any more. Simply specify basic data and select trading parameters: account type, deposit, leverage, and hedging ability.



  5. Added automatic allocation of a demo account for quick start. If the platform has no accounts yet, a demo account on the first available trade server is allocated during the launch. After successful opening, connection to the account is established immediately.

  6. Now, each position has a ticket — a unique number. It usually matches the ticket of an order used to open the position except when the ticket is changed as a result of service operations on the server, for example, when charging swaps with position re-opening. A ticket is assigned automatically to all available positions after the terminal update.



  7. Fixed setting Stop Loss and Take Profit levels when placing a market order leading to a position reversal. Until recently, no appropriate levels were set for a new position.
  8. Fixed displaying prices with four and more decimal places on the one-click trading panel elements.
  9. Fixed displaying news in the print preview window.
  10. Fixed tick chart display.
  11. Fixed opening the Market Depth after the terminal emergency shutdown.
  12. Added a check if market orders are allowed when displaying one-click trading panel control elements.
  13. Optimized profit and margin calculation in case of a large number of open orders and positions.
  14. Added translation of the user interface into Malay.
  15. Fully revised the user manual. New design, interactive screenshots and embedded videos — learn trading in MetaTrader 5 with maximum convenience:



  16. Fixed display of graphical objects in the "Chart on foreground" mode.

Tester

  1. Added ability to test trading robots and technical indicators in real tick history.

    Testing and optimization on real ticks are as close to real conditions as possible. Instead of generated ticks based on minute data, it is possible to use real ticks accumulated by a broker. These are ticks from exchanges and liquidity providers.

    To start testing or optimization in real ticks, select the appropriate mode in the strategy tester:



    Tick data has greater size compared to minute one. Downloading it may take quite a long time during the first test. Downloaded tick data is stored by months in TKC files in \bases\[trade server name]\ticks\[symbol name]\.

    Testing on real ticks
    When testing on real ticks, a spread may change within a minute bar, whereas when generating ticks within a minute, a spread fixed in the appropriate bar is used.

    If the Market Depth is displayed for a symbol, the bars are built strictly according to the last executed trade price (Last). Otherwise, the tester first attempts to build the bars by Last prices, and in case of their absence, uses Bid ones. OnTick event is triggered on all ticks regardless of whether the Last price is present or not.

    Please note that trading operations are always performed by Bid and Ask prices even if the chart is built by Last prices. For example, if an Expert Advisor using only bar open prices for trading (i.e., the built-in Moving Average) receives a signal at Last price, it performs a trade at another price (Bid or Ask depending on the direction). If "Every tick" mode is used, the bars are built by Bid prices, while trades are performed by Bid and Ask ones. The Ask price is calculated as Bid + fixed spread of a corresponding minute bar.

    If a symbol history has a minute bar with no tick data for it, the tester generates ticks in the "Every tick" mode. This allows testing the EA on a certain period in case a broker's tick data is insufficient. If a symbol history has no minute bar but the appropriate tick data for the minute is present, these ticks are ignored. The minute data is considered more reliable.

    Testing on real ticks in the MQL5 Cloud Network
    Testing on real ticks is available not only on local and remote agents, but also through the MQL5 Cloud Network. Optimization of a strategy that could take months, can be completed in a few hours using the computing power of thousands of computers.

    To test a strategy using the MQL5 Cloud Network, enable the use of cloud agents:



    Tests on real ticks using the MQL5 Cloud Network can consume a lot of data. This can significantly affect the payment for the use of the network power.
  2. Fixed an error that hindered the calculation of commission on several trading symbol types.
  3. Fixed filling Expert field for trading orders resulting from SL/TP activation according to the Expert field of the corresponding position. Previously, it was not filled.
  4. Fixed switching to usual and forward optimization results' tabs.
  5. Fixed calculation and display of the "Envelopes" indicator.
  6. Optimized visual testing.
  7. Optimized profit and margin calculation in case of a large number of open orders and positions.
  8. Optimized trading operations during high-frequency trading.
  9. Now, history synchronization is not performed if a request for non-critical symbol's properties (not requiring the current quotes) has been made. For example, SYMBOL_SELECT, SYMBOL_DIGITS, SYMBOL_SPREAD_FLOAT, SYMBOL_TRADE_CALC_MODE, SYMBOL_TRADE_MODE, SYMBOL_TRADE_STOPS_LEVEL, SYMBOL_TRADE_FREEZE_LEVEL, SYMBOL_TRADE_EXEMODE, etc. Previously, the non-critical symbol history was synchronized at any request for its property.
  10. Fixed calculation of swaps as a percentage per annum.

MQL5

  1. The format of the executable EX5 files has changed to implement the new features of the MQL5 language and the new hedging option in MetaTrader 5. All EX5 applications compiled in previous builds of MetaEditor will work properly after the update, i.e. the upward compatibility is fully preserved.

    EX5 programs compiled in build 1325 and above will not run in old terminal builds - backward compatibility is not supported.

  2. Added support for abstract classes and pure virtual functions.

    Abstract classes are used for creating generic entities that you expect to use for creating more specific derived classes. An abstract class can only be used as the base class for some other class, that is why it is impossible to create an object of the abstract class type.

    A class which contains at least one pure virtual function in it is abstract. Therefore, classes derived from the abstract class must implement all its pure virtual functions, otherwise they will also be abstract classes.

    A virtual function is declared as "pure" by using the pure-specifier syntax. Consider the example of the CAnimal class, which is only created to provide common functions – the objects of the CAnimal type are too general for practical use. Thus, CAnimal is a good example for an abstract class:
    class CAnimal
      {
    public:
                          CAnimal();     // Constructor
       virtual void       Sound() = 0;   // A pure virtual function
    private:
       double             m_legs_count;  // How many feet the animal has
      };
    Here Sound() is a pure virtual function, because it is declared with the specifier of the pure virtual function PURE (=0).

    Pure virtual functions are only the virtual functions for which the PURE specifier is set: (=NULL) or (=0). Example of abstract class declaration and use:
    class CAnimal
      {
    public:
       virtual void       Sound()=NULL;   // PURE method, should be overridden in the derived class, CAnimal is now abstract and cannot be created
      };
    //--- Derived from an abstract class
    class CCat : public CAnimal
     {
    public:
      virtual void        Sound() { Print("Myau"); } // PURE is overridden, CCat is not abstract and can be created
     };
    
    //--- examples of wrong use
    new CAnimal;         // Error of 'CAnimal' - the compiler returns the "cannot instantiate abstract class" error
    CAnimal some_animal; // Error of 'CAnimal' - the compiler returns the "cannot instantiate abstract class" error
    
    //--- examples of correct use
    new CCat;  // no error - the CCat class is not abstract
    CCat cat;  // no error - the CCat class is not abstract
    Restrictions on abstract classes
    If the constructor for an abstract class calls a pure virtual function (either directly or indirectly), the result is undefined.
    //+------------------------------------------------------------------+
    //| An abstract base class                                           |
    //+------------------------------------------------------------------+
    class CAnimal
      {
    public:
       //--- a pure virtual function
       virtual void      Sound(void)=NULL;
       //--- function
       void              CallSound(void) { Sound(); }
       //--- constructor
       CAnimal()
        {
         //--- an explicit call of the virtual method
         Sound();
         //--- an implicit call (using a third function)
         CallSound();
         //--- a constructor and/or destructor always calls its own functions,
         //--- even if they are virtual and overridden by a called function in a derived class
         //--- if the called function is purely virtual
         //--- the call causes the "pure virtual function call" critical execution error
        }
      };
    However, constructors and destructors for abstract classes can call other member functions.

  3. Added support for pointers to functions to simplify the arrangement of event models.

    To declare a pointer to a function, specify the "pointer to a function" type, for example:
    typedef int (*TFunc)(int,int);
    Now, TFunc is a type, and it is possible to declare the variable pointer to the function:
    TFunc func_ptr;
    The func_ptr variable may store the function address to declare it later:
    int sub(int x,int y) { return(x-y); }
    int add(int x,int y) { return(x+y); }
    int neg(int x)       { return(~x);  }
    
    func_ptr=sub;
    Print(func_ptr(10,5));
    
    func_ptr=add;
    Print(func_ptr(10,5));
    
    func_ptr=neg;           // error: neg is not of  int (int,int) type
    Print(func_ptr(10));    // error: there should be two parameters
    Pointers to functions can be stored and passed as parameters. You cannot get a pointer to a non-static class method.

  4. MqlTradeRequest features two new fields:

    • position — position ticket. Fill it when changing and closing a position for its clear identification while trading in hedging mode. In the netting system, filling the field does not affect anything since positions are identified by a symbol name.
    • position_by — opposite position ticket. It is used when closing a position by an opposite one (opened at the same symbol but in the opposite direction). The ticket is used only in the hedging system.

  5. Added TRADE_ACTION_CLOSE_BY value to the ENUM_TRADE_REQUEST_ACTIONS enumeration of trading operation types — close a position by an opposite one. The ticket is used only in the hedging system.

  6. Added trading operation tickets to the enumerations of the appropriate order, deal, and position properties:

    • Added ORDER_TICKET property to ENUM_ORDER_PROPERTY_INTEGER — order ticket. Unique number assigned to each order.
    • Added DEAL_TICKET property to ENUM_DEAL_PROPERTY_INTEGER — deal ticket. Unique number assigned to each deal.
    • Added POSITION_TICKET property to ENUM_POSITION_PROPERTY_INTEGER — position ticket. Unique number assigned to each newly opened position. It usually matches the ticket of an order used to open the position except when the ticket is changed as a result of service operations on the server, for example, when charging swaps with position re-opening. To find an order used to open a position, apply the POSITION_IDENTIFIER property. POSITION_TICKET value corresponds to MqlTradeRequest::position.

  7. Added ORDER_TYPE_CLOSE_BY value to the ENUM_ORDER_TYPE order type enumeration — close by order.
  8. Added ORDER_POSITION_BY_ID value to the ENUM_ORDER_PROPERTY_INTEGER order property enumeration — opposite position identifier for ORDER_TYPE_CLOSE_BY type orders.
  9. Added DEAL_ENTRY_OUT_BY value to the ENUM_DEAL_ENTRY deal direction enumeration — a deal is performed as a result of a close by operation.
  10. MqlTradeTransaction also features the two similar fields:

    • position — ticket of a position affected by transaction. It is filled for transactions related to handling market orders (TRADE_TRANSACTION_ORDER_* except TRADE_TRANSACTION_ORDER_ADD, where a position ticket is not assigned yet) and order history (TRADE_TRANSACTION_HISTORY_*).
    • position_by — opposite position ticket. It is used when closing a position by an opposite one (opened at the same symbol but in the opposite direction). It is filled only for orders closing a position by an opposite one (close by) and deals closing by an opposite one (out by).

  11. Added PositionGetTicket function — return a position ticket by an index in the list of open positions and automatically select that position for further work using the PositionGetDouble, PositionGetInteger, and PositionGetString functions.
    ulong  PositionGetTicket(
       int  index      // index in the list of positions
       );

  12. Added PositionSelectByTicket function — select an open position for further work by a specified ticket.
    bool  PositionSelectByTicket(
       ulong   ticket     // position ticket
       );

  13. Added SYMBOL_MARGIN_HEDGED value to the ENUM_SYMBOL_INFO_DOUBLE trade symbol property enumeration — size of a contract or margin for one lot of hedged positions (oppositely directed positions at one symbol).

    • If the initial margin (SYMBOL_MARGIN_INITIAL) is specified for a symbol, the hedged margin is specified as an absolute value (in monetary terms).
    • If the initial margin is not set (equal to 0), a contract size to be used in the margin calculation is specified in SYMBOL_MARGIN_HEDGED. The margin is calculated using the equation that corresponds to a trade symbol type (SYMBOL_TRADE_CALC_MODE).

    Margin calculation for hedged positions is described in details in the MetaTrader 5 trading platform Help.

  14. Added ACCOUNT_MARGIN_MODE value to the ENUM_ACCOUNT_INFO_INTEGER account property enumeration — mode of margin calculation for the current trading account:

    • ACCOUNT_MARGIN_MODE_RETAIL_NETTING — used for the over-the-counter market when accounting positions in the netting mode (one position per symbol). Margin calculation is based on a symbol type (SYMBOL_TRADE_CALC_MODE).
    • ACCOUNT_MARGIN_MODE_EXCHANGE — used on the exchange markets. Margin calculation is based on the discounts specified in symbol settings. Discounts are set by the broker, however they cannot be lower than the exchange set values.
    • ACCOUNT_MARGIN_MODE_RETAIL_HEDGING — used for the over-the-counter market with independent position accounting (hedging, there can be multiple positions at a single symbol). Margin calculation is based on a symbol type (SYMBOL_TRADE_CALC_MODE). The hedged margin size (SYMBOL_MARGIN_HEDGED) is also considered.

  15. Added TERMINAL_SCREEN_DPI value to the ENUM_TERMINAL_INFO_INTEGER client terminal property enumeration — data display resolution is measured in dots per inch (DPI). Knowledge of this parameter allows specifying the size of graphical objects, so that they look the same on monitors with different resolution.

  16. Added TERMINAL_PING_LAST value to the ENUM_TERMINAL_INFO_INTEGER client terminal properties — the last known value of a ping to a trade server in microseconds. One second comprises of one million microseconds.

  17. Fixed return of the SendFTP function call result. Previously, FALSE was returned after a successful sending instead of TRUE.
  18. MQL5: Fixed an error in StringConcatenate function that occasionally caused "Access violation" execution error.
  19. Fixed a few errors occurred when working with template functions.
  20. Added ability to display lines exceeding 4000 characters for Print, Alert, and Comment functions.
  21. Fixed an error in ArrayCompare function that occurred when comparing an array to itself but with different initial position shift from the beginning.
  22. Added support for hedging to Standard Library:

    CPosition
    Added methods:

    • SelectByMagic — select position by a magic number and symbol for further work.
    • SelectByTicket — select position by a ticket for further work.

    CTrade
    Added methods:

    • RequestPosition — receive a position ticket.
    • RequestPositionBy — receive an opposite position ticket.
    • PositionCloseBy — close a position with the specified ticket by an opposite position.
    • SetMarginMode — set margin calculation mode according to the current account settings.

    Added overloading for the methods:

    • PositionClose — close position by ticket.
    • PositionModify — modify position by ticket.

    CAccountInfo
    Changed the methods:

    • MarginMode — receive margin calculation mode. Until recently, the method worked similarly to the new StopoutMode method.
    • MarginDescription — receive margin calculation mode as a string. Until recently, the method worked similarly to the new StopoutModeDescription method.

    Added methods:

    • StopoutMode — receive minimum margin level specification mode.
    • StopoutModeDescription — receive minimum margin level specification mode as a string.

    CExpert
    Added methods:

    • SelectPosition — select a position for further work.

  23. Added a few improvements to the Standard Library.
  24. Fixed unloading of DLLs.
  25. Added support for template class constructors.

Signals

  1. Fixed a few trading signals showcase display errors.

MetaEditor

  1. Fixed search of words by files in "Match Whole Word Only" mode.
  2. Added moving to a file by double-clicking on the necessary file's compilation result line.
  3. Fixed display of some control elements in Windows XP.
Updated documentation.
1 April 2016
MetaTrader 5 Platform Build 1295

Terminal

  1. In order to expand possibilities of retail Forex traders, we have added the second accounting system — hedging. Now, it is possible to have multiple positions per symbol, including oppositely directed ones. This paves the way to implementing trading strategies based on the so-called "locking" — if the price moves against a trader, they can open a position in the opposite direction.

    Since the new system is similar to the one used in MetaTrader 4, it will be familiar to traders. At the same time, traders will be able to enjoy all the advantages of the fifth platform version — filling orders using multiple deals (including partial fills), multicurrency and multithreaded tester with support for MQL5 Cloud Network, and much more.

    Now, you can use one account to trade the markets that adhere to the netting system and allow having only one position per instrument, and use another account in the same platform to trade Forex and apply hedging.

    Opening a hedge account and viewing position accounting type
    A position accounting system is set at an account level and displayed in the terminal window header and the Journal:



    To open a demo account with hedging, enable the appropriate option:




    Netting system
    With this system, you can have only one common position for a symbol at the same time:

    • If there is an open position for a symbol, executing a deal in the same direction increases the volume of this position.
    • If a deal is executed in the opposite direction, the volume of the existing position can be decreased, the position can be closed (when the deal volume is equal to the position volume) or reversed (if the volume of the opposite deal is greater than the current position).


    It does not matter, what has caused the opposite deal — an executed market order or a triggered pending order.

    The below example shows execution of two EURUSD Buy deal 0.5 lots each:


    Execution of both deals resulted in one common position of 1 lot.

    Hedging system
    With this system, you can have multiple open positions of one and the same symbol, including opposite position.

    If you have an open position for a symbol, and execute a new deal (or a pending order triggers), a new position is additionally opened. Your current position does not change.

    The below example shows execution of two EURUSD Buy deal 0.5 lots each:


    Execution of these deals resulted in opening two separate positions.

    New trade operation type - Close By
    The new trade operation type has been added for hedging accounts — closing a position by an opposite one. This operation allows closing two oppositely directed positions at a single symbol. If the opposite positions have different numbers of lots, only one order of the two remains open. Its volume will be equal to the difference of lots of the closed positions, while the position direction and open price will match (by volume) the greater of the closed positions.

    Compared with a single closure of the two positions, the closing by an opposite position allows traders to save one spread:

    • In case of a single closing, traders have to pay a spread twice: when closing a buy position at a lower price (Bid) and closing a sell position at a higher one (Ask).
    • When using an opposite position, an open price of the second position is used to close the first one, while an open price of the first position is used to close the second one.


    In the latter case, a "close by" order is placed. Tickets of closed positions are specified in its comment. A pair of opposite positions is closed by two "out by" deals. Total profit/loss resulting from closing the both positions is specified only in one deal.



  2. Added ability to test trading robots and technical indicators in real tick history.

    Testing and optimization on real ticks are as close to real conditions as possible. Instead of generated ticks based on minute data, it is possible to use real ticks accumulated by a broker. These are ticks from exchanges and liquidity providers.

    To start testing or optimization in real ticks, select the appropriate mode in the strategy



    Tick data has greater size compared to minute one. Downloading it may take quite a long time during the first test. Downloaded tick data is stored by months in TKC files in \bases\[trade server name]\ticks\[symbol name]\.

    Testing on real ticks
    When testing on real ticks, a spread may change within a minute bar, whereas when generating ticks within a minute, a spread fixed in the appropriate bar is used.

    If the Market Depth is displayed for a symbol, the bars are built strictly according to the last executed trade price (Last). Otherwise, the tester first attempts to build the bars by Last prices, and in case of their absence, uses Bid ones. OnTick event is triggered on all ticks regardless of whether the Last price is present or not.

    Please note that trading operations are always performed by Bid and Ask prices even if the chart is built by Last prices. For example, if an Expert Advisor using only bar open prices for trading (i.e., the built-in Moving Average) receives a signal at Last price, it performs a trade at another price (Bid or Ask depending on the direction). If "Every tick" mode is used, the bars are built by Bid prices, while trades are performed by Bid and Ask ones. The Ask price is calculated as Bid + fixed spread of a corresponding minute bar.

    If a symbol history has a minute bar with no tick data for it, the tester generates ticks in the "Every tick" mode. This allows testing the EA on a certain period in case a broker's tick data is insufficient. If a symbol history has no minute bar but the appropriate tick data for the minute is present, these ticks are ignored. The minute data is considered more reliable.
    Currently, testing and optimization on real ticks are possible only on local and remote agents. Support for MQL5 Cloud Network will be added in the near future.

  3. Added the Chat. Now, you can communicate with your MQL5.community friends and colleagues. The chat displays all personal messages from your MQL5 account. To start communicating, log in to your account directly from the chat window or via the platform settings: Tools -> Options -> Community.




  4. Simplified demo account creation dialog, added ability to create hedge accounts. You do not have to fill the large form any more. Simply specify basic data and select trading parameters: account type, deposit, leverage, and hedging ability.



  5. Added automatic allocation of a demo account for quick start. If the platform has no accounts yet, a demo account on the first available trade server is allocated during the launch. After successful opening, connection to the account is established immediately.

  6. Now, each position has a ticket — a unique number. It usually matches the ticket of an order used to open the position except when the ticket is changed as a result of service operations on the server, for example, when charging swaps with position re-opening. A ticket is assigned automatically to all available positions after the terminal update.




  7. Fixed setting Stop Loss and Take Profit levels when placing a market order leading to a position reversal. Until recently, no appropriate levels were set for a new position.
  8. Fixed displaying prices with four and more decimal places on the one-click trading panel elements.
  9. Fixed displaying news in the print preview window.
  10. Fixed tick chart display.
  11. Fixed opening the Market Depth after the terminal emergency shutdown.
  12. Added a check if market orders are allowed when displaying one-click trading panel control elements.
  13. Optimized profit and margin calculation in case of a large number of open orders and positions.
  14. Added translation of the user interface into Malay.
  15. Fully revised the user manual. New design, interactive screenshots and embedded videos — learn trading in MetaTrader 5 with maximum convenience:




MQL5

  1. Added support for abstract classes and pure virtual functions.

    Abstract classes are used for creating generic entities, that you expect to use for creating more specific derived classes. An abstract class can only be used as the base class for some other class, that is why it is impossible to create an object of the abstract class type.

    A class which contains at least one pure virtual function in it is abstract. Therefore, classes derived from the abstract class must implement all its pure virtual functions, otherwise they will also be abstract classes.

    A virtual function is declared as "pure" by using the pure-specifier syntax. Consider the example of the CAnimal class, which is only created to provide common functions – the objects of the CAnimal type are too general for practical use. Thus, CAnimal is a good example for an abstract class:
    class CAnimal
      {
    public:
                          CAnimal();     // constructor
       virtual void       Sound() = 0;   // pure virtual function
    private:
       double             m_legs_count;  // number of animal legs
      };
    Here Sound() is a pure virtual function, because it is declared with the specifier of the pure virtual function PURE (=0).

    Pure virtual functions are only the virtual functions for which the PURE specifier is set: (=NULL) or (=0). Example of abstract class declaration and use:
    class CAnimal
      {
    public:
       virtual void       Sound()=NULL;   // PURE method, should be overridden in the derived class, CAnimal is now abstract and cannot be created
      };
    //--- descendant from the abstract class
    class CCat : public CAnimal
     {
    public:
      virtual void        Sound() { Print("Myau"); } // PURE is overridden, CCat is not abstract and can be created
     };
    
    //--- examples of wrong use
    new CAnimal;         // Error of 'CAnimal' - the compiler returns the "cannot instantiate abstract class" error
    CAnimal some_animal; // Error of 'CAnimal' - the compiler returns the "cannot instantiate abstract class" error
    
    //--- examples of correct use
    new CCat;  // no error - the CCat class is not abstract
    CCat cat;  // no error - the CCat class is not abstract
    Restrictions on abstract classes
    If the constructor for an abstract class calls a pure virtual function (either directly or indirectly), the result is undefined.
    //+------------------------------------------------------------------+
    //| An abstract base class                                           |
    //+------------------------------------------------------------------+
    class CAnimal
      {
    public:
       //--- a pure virtual function
       virtual void      Sound(void)=NULL;
       //--- function
       void              CallSound(void) { Sound(); }
       //--- constructor
       CAnimal()
        {
         //--- an explicit call of the virtual method
         Sound();
         //--- an implicit call (using a third function)
         CallSound();
         //--- a constructor and/or destructor always calls its own functions,
         //--- even if they are virtual and overridden by a called function in a derived class
         //--- if the called function is purely virtual
         //--- the call causes the "pure virtual function call" critical execution error
        }
      };
    However, constructors and destructors for abstract classes can call other member functions.

  2. Added support for pointers to functions to simplify the arrangement of event models.

    To declare a pointer to a function, specify the "pointer to a function" type, for example:
    typedef int (*TFunc)(int,int);
    Now, TFunc is a type, and it is possible to declare the variable pointer to the function:
    TFunc func_ptr;
    The func_ptr variable may store the function address to declare it later:
    int sub(int x,int y) { return(x-y); }
    int add(int x,int y) { return(x+y); }
    int neg(int x)       { return(~x);  }
    
    func_ptr=sub;
    Print(func_ptr(10,5));
    
    func_ptr=add;
    Print(func_ptr(10,5));
    
    func_ptr=neg;           // error: neg is not of  int (int,int) type
    Print(func_ptr(10));    // error: there should be two parameters
    Pointers to functions can be stored and passed as parameters. You cannot get a pointer to a non-static class method.

  3. MqlTradeRequest features two new fields:

    • position — position ticket. Fill it when changing and closing a position for its clear identification while trading in hedging mode. In the netting system, filling the field does not affect anything since positions are identified by a symbol name.
    • position_by — opposite position ticket. It is used when closing a position by an opposite one (opened at the same symbol but in the opposite direction). The ticket is used only in the hedging system.

  4. Added TRADE_ACTION_CLOSE_BY value to the ENUM_TRADE_REQUEST_ACTIONS enumeration of trading operation types — close a position by an opposite one. The ticket is used only in the hedging system.

  5. Added trading operation tickets to the enumerations of the appropriate order, deal, and position properties:

    • Added ORDER_TICKET property to ENUM_ORDER_PROPERTY_INTEGER — order ticket. Unique number assigned to each order.
    • Added DEAL_TICKET property to ENUM_DEAL_PROPERTY_INTEGER — deal ticket. Unique number assigned to each deal.
    • Added POSITION_TICKET property to ENUM_POSITION_PROPERTY_INTEGER — position ticket. Unique number assigned to each newly opened position. It usually matches the ticket of an order used to open the position except when the ticket is changed as a result of service operations on the server, for example, when charging swaps with position re-opening. To find an order used to open a position, apply the POSITION_IDENTIFIER property. POSITION_TICKET value corresponds to MqlTradeRequest::position.

  6. Added ORDER_TYPE_CLOSE_BY value to the ENUM_ORDER_TYPE order type enumeration — close by order.
  7. Added ORDER_POSITION_BY_ID value to the ENUM_ORDER_PROPERTY_INTEGER order property enumeration — opposite position identifier for ORDER_TYPE_CLOSE_BY type orders.
  8. Added DEAL_ENTRY_OUT_BY value to the ENUM_DEAL_ENTRY deal direction enumeration — a deal is performed as a result of a close by operation.
  9. MqlTradeTransaction also features the two similar fields:

    • position — ticket of a position affected by transaction. It is filled for transactions related to handling market orders (TRADE_TRANSACTION_ORDER_* except TRADE_TRANSACTION_ORDER_ADD, where a position ticket is not assigned yet) and order history (TRADE_TRANSACTION_HISTORY_*).
    • position_by — opposite position ticket. It is used when closing a position by an opposite one (opened at the same symbol but in the opposite direction). It is filled only for orders closing a position by an opposite one (close by) and deals closing by an opposite one (out by).

  10. Added PositionGetTicket function — return a position ticket by an index in the list of open positions and automatically selects that position for further work using the PositionGetDouble, PositionGetInteger, and PositionGetString functions.
    ulong  PositionGetTicket(
       int  index      // index in the list of positions
       );

  11. Added PositionSelectByTicket function — select an open position for further work by a specified ticket.
    bool  PositionSelectByTicket(
       ulong   ticket     // position ticket
       );

  12. Added SYMBOL_MARGIN_HEDGED value to the ENUM_SYMBOL_INFO_DOUBLE trade symbol property enumeration — size of a contract or margin for one lot of hedged positions (oppositely directed positions at one symbol).

    • If the initial margin (SYMBOL_MARGIN_INITIAL) is specified for a symbol, the hedged margin is specified as an absolute value (in monetary terms).
    • If the initial margin is not set (equal to 0), a contract size to be used in the margin calculation is specified in SYMBOL_MARGIN_HEDGED. The margin is calculated using the equation that corresponds to a trade symbol type (SYMBOL_TRADE_CALC_MODE).

    Margin calculation for hedged positions is described in details in the MetaTrader 5 trading platform Help.

  13. Added ACCOUNT_MARGIN_MODE value to the ENUM_ACCOUNT_INFO_INTEGER account property enumeration — mode of margin calculation for the current trading account:

    • ACCOUNT_MARGIN_MODE_RETAIL_NETTING — used for the over-the-counter market when accounting positions in the netting mode (one position per symbol). Margin calculation is based on a symbol type (SYMBOL_TRADE_CALC_MODE).
    • ACCOUNT_MARGIN_MODE_EXCHANGE — used on the exchange markets. Margin calculation is based on the discounts specified in symbol settings. Discounts are set by the broker, however they cannot be lower than the exchange set values.
    • ACCOUNT_MARGIN_MODE_RETAIL_HEDGING — used for the over-the-counter market with independent position accounting (hedging, there can be multiple positions at a single symbol). Margin calculation is based on a symbol type (SYMBOL_TRADE_CALC_MODE). The hedged margin size (SYMBOL_MARGIN_HEDGED) is also considered.

  14. Added TERMINAL_SCREEN_DPI value to the ENUM_TERMINAL_INFO_INTEGER client terminal property enumeration — data display resolution is measured in dots per inch (DPI). Knowledge of this parameter allows specifying the size of graphical objects, so that they look the same on monitors with different resolution.

  15. Added TERMINAL_PING_LAST value to the ENUM_TERMINAL_INFO_INTEGER client terminal properties — the last known value of a ping to a trade server in microseconds. One second comprises of one million microseconds.

  16. Fixed return of the SendFTP function call result. Previously, FALSE was returned after a successful sending instead of TRUE.
  17. Fixed an error in StringConcatenate function that occasionally caused "Access violation" execution error.
  18. Fixed a few errors occurred when working with template functions.
  19. Added ability to display lines exceeding 4000 characters for Print, Alert, and Comment functions.
  20. Fixed an error in ArrayCompare function that occurred when comparing an array to itself but with different initial position shift from the beginning.
  21. Added support for hedging to Standard Library:

    CPosition
    Added methods:

    • SelectByMagic — select position by a magic number and symbol for further work.
    • SelectByTicket — select position by a ticket for further work.

    CTrade
    Added methods:

    • RequestPosition — receive a position ticket.
    • RequestPositionBy — receive an opposite position ticket.
    • PositionCloseBy — close a position with the specified ticket by an opposite position.
    • SetMarginMode — set margin calculation mode according to the current account settings.

    Added overloading for the methods:

    • PositionClose — close position by ticket.
    • PositionModify — modify position by ticket.

    CAccountInfo
    Changed the methods:

    • MarginMode — receive margin calculation mode. Until recently, the method worked similarly to the new StopoutMode method.
    • MarginDescription — receive margin calculation mode as a string. Until recently, the method worked similarly to the new StopoutModeDescription method.

    Added methods:

    • StopoutMode — receive minimum margin level specification mode.
    • StopoutModeDescription — receive minimum margin level specification mode as a string.

    CExpert
    Added methods:

    • SelectPosition — select a position for further work.

  22. Added a few improvements to the Standard Library.


Signals

  1. Fixed a few trading signals showcase display errors.


Tester

  1. Fixed an error that hindered the calculation of commission on several trading symbol types.
  2. Fixed filling Expert field for trading orders resulting from SL/TP activation according to the Expert field of the corresponding position. Previously, it was not filled.
  3. Fixed switching to usual and forward optimization results' tabs.
  4. Fixed calculation and display of the "Envelopes" indicator.
  5. Optimized visual testing.
  6. Optimized profit and margin calculation in case of a large number of open orders and positions.
  7. Optimized trading operations during high-frequency trading.
  8. Now, history synchronization is not performed if a request for non-critical symbol's properties (not requiring the current quotes) has been made. For example, SYMBOL_SELECT, SYMBOL_DIGITS, SYMBOL_SPREAD_FLOAT, SYMBOL_TRADE_CALC_MODE, SYMBOL_TRADE_MODE, SYMBOL_TRADE_STOPS_LEVEL, SYMBOL_TRADE_FREEZE_LEVEL, SYMBOL_TRADE_EXEMODE, etc. Previously, the non-critical symbol history was synchronized at any request for its property.

MetaEditor

  1. Fixed search of words by files in "Match Whole Word Only" mode.
  2. Added moving to a file by double-clicking on the necessary file's compilation result line.
  3. Fixed display of some control elements in Windows XP.


Updated documentation.
31 March 2016
MetaTrader 5 iOS build 1261
  1. The trading platform now additionally supports the second position accounting system — Hedging. The new system allows opening multiple positions of the same financial instrument, including opposite positions. Now, the platform provides both exchange trading with the netting system and Forex trading with one of the two available systems.

    The new position accounting system is similar to that of MetaTrader 4, combined with all the advantages of the fifth-generation platform — execution of orders using multiple deals (including partial filling), stop-limit orders, and more.

    Update the platform right now to see how the hedging option works. When opening a new demo account, enable the \"Use hedge\" option. The option will be available if your broker's server has already been updated and configured.

  2. Also, the new version includes minor bug fixes and improvements.
31 March 2016
MetaTrader 5 Android build 1262
  1. The trading platform now additionally supports the second position accounting system — Hedging. The new system allows opening multiple positions of the same financial instrument, including opposite positions. Now, the platform provides both exchange trading with the netting system and Forex trading with one of the two available systems.

    The new position accounting system is similar to that of MetaTrader 4, combined with all the advantages of the fifth-generation platform — execution of orders using multiple deals (including partial filling), stop-limit orders, and more.

    Update the platform right now to see how the hedging option works. When opening a new demo account, enable the "Use hedge" option. The option will be available if your broker's server has already been updated and configured.

  2. Also, the new version includes minor bug fixes and improvements.
12 February 2016
MetaTrader 5 Android build 1224
  • A new window has been added to the tablet version to show the detailed information about trading operations. Tap on an order or a trade to view its Open and Close time to the nearest second, a comment and the amount of the broker's commission.
  • Improved news section. Select news categories to follow what is interesting for you. Add the news items you like to Favorites to quickly access them wherever you need.
  • Added period separators to show the borders of higher timeframes on a chart.
  • Added display of the Ask line on a chart.
  • New interface languages: Korean and Vietnamese.
  • Increased maximum number of objects on a chart.
  • Various bug fixes and improvements.
3 February 2016
MetaTrader 5 iOS build 1225
  • Added portrait mode for iPad. Now, you can browse through long lists of trading operations, as well as read your mail and financial news more conveniently.
  • Added native support for iPad Pro.
  • Added Korean language.
17 December 2015
MetaTrader 5 Platform Build 1240: Faster operation and embedded videos

Virtual Hosting

  1. Added a link to the tutorial video "How to Rent A Virtual Platform" into the Virtual Hosting Wizard dialog. Watch this two-minute video to learn how to easily launch a trading robot or copy signals 24/7.


    This video as well as many others is available on the official MetaQuotes Software Corp. YouTube channel.
  2. Fixed migration for hosting when a custom indicator is called or an EX5 library within a custom indicator is called from an Expert Advisor.

Terminal

  1. Accelerated update of the list of open orders and positions during high-frequency trading (50 and more operations per second).
  2. Optimized and greatly accelerated initial synchronization of the terminal with a trade server in case of a large amount of symbols (tens of thousands). Now, you can start working much faster after connection is established.
  3. Optimized and significantly reduced memory consumption by the terminal.
  4. Added saving and restoring the depth of market settings when closing/opening the terminal.
  5. Fixed artifacts that occurred in Windows 10 when dragging the terminal windows.
  6. Fixed the context help for a number of commands and dialogs. For activating help concerning a certain element, move the cursor on it and press F1.
  7. The works on adapting the interface for high resolution screens (4K) are underway.

MQL5

  1. Added the new properties for the OrderGetString, HistoryOrderGetString, and HistoryDealGetString functions responsible for receiving data on orders and deals:

    • ORDER_EXTERNAL_ID - order ID in an external trading system (on the exchange).
    • DEAL_EXTERNAL_ID - deal ID in an external trading system.

  2. Fixed the ZeroMemory function operation when working with structures and classes. Memory clearing was not performed in some cases.
  3. Added the error codes during the SendFTP function operation. The function sends the file to the address specified on the FTP tab of the Options window.

    • ERR_FTP_NOSERVER - FTP server is not specified in the settings
    • ERR_FTP_NOLOGIN - FTP login is not specified in the settings
    • ERR_FTP_FILE_ERROR - file does not exist
    • ERR_FTP_CONNECT_FAILED - failed to connect to the FTP server
    • ERR_FTP_CHANGEDIR - file upload directory not found on the FTP server
    • ERR_FTP_CLOSED - connection to the FTP server closed

  4. Fixed type casting access by inheritance between child class objects and their parents.
  5. Fixed a few errors in the class templates.
  6. Fixed requesting ticks using the CopyTicks function. When specifying the COPY_TICKS_TRADE parameter (copy only trade ticks) for consecutive identical trade ticks (identical volume and last price), only the first tick was passed.
  7. Fixed defining a size of a custom type variable.
  8. Fixed an error when using ZLib in the CryptDecode function that led to an infinite unzip loop.

Tester

  1. Fixed synchronization of the price history for a symbol different from the main test one.
  2. Fixed doubling of the TRADE_TRANSACTION_DEAL_ADD transaction (adding a trade to history) in the OnTradeTransaction event handler.
  3. Changed forward test behavior during genetic optimization. Now, all unique results obtained after genetic optimization participate in forward passes. Previously, only 1/4 of the results were used.

MetaEditor

  1. MetaEditor: Added a link to the tutorial video "How to Create a Trading Robot in the MQL5 Wizard" to the MQL5 Wizard. Watch this three-minute video and develop a trading robot without writing a single line of code.


    This video as well as many others is available on the official MetaQuotes Software Corp. YouTube channel.
  2. Fixed window arrangement commands if one of the windows is fully expanded. The Window menu allows you to arrange open files as tiles, vertically, horizontally and as a cascade.
  3. The works on adapting the interface for high resolution screens (4K) are underway.
Updated documentation.
19 November 2015
MetaTrader 5 Android Build 1172
  1. Improved symbol chart zoom: increased the amount of zoom steps and enhanced display smoothness.

    MetaTrader 5 Android Build 1172: Convenient Chart Zoom and Accrued Interest in the Bond Properties

  2. All changes in the set of symbols and their sequence in the Market Watch and chart settings (scale, color scheme, object and indicator lists) are saved after closing the application in any way.
  3. Added a face value and accrued interest in bond properties.
11 November 2015
MetaTrader 5 iPhone build 1171
Bug fixes and improvements.
30 October 2015
MetaTrader 5 Build 1210: Enhanced Depth of Market and General Improvements

Terminal

  1. Terminal: Added ability to place limit orders at a price worse than the market one in the Depth of Market. This allows you to get a guaranteed order execution at a specified price on the market.

    If we drag a limit order through ask/bid border, it will change to a stop order (Buy Limit will be replaced by Buy Stop, while Sell Limit - by Sell Stop). Hold Crtl while dragging so that a limit order is not replaced by a stop one.




  2. Terminal: Added the "Show quick trading buttons" option in the chart settings. It allows you to hide the One Click Trading panel enabling buttons and the Depth of Market from a chart.




  3. Terminal: Fixed occasional conflicts between tooltips and other applications.

MQL5

  1. MQL5: Fixed the operation of the Copy* functions for copying history data with dynamic arrays having the AS_SERIES flag. The flag is set by the ArraySetAsSeries function and indicates that indexation of the array elements is performed as in timeseries.
  2. MQL5: Changed the CHART_SHOW_ONE_CLICK property managed via ChartSetInteger and ChartGetInteger. Previously, the property allowed showing/hiding the One Click Trading panel on a chart. Now, it also shows/hides the buttons for setting the One Click Trading panel and the Depth of Market on a chart (similar to the "Show quick trading buttons" in the chart settings).
  3. MQL5: Fixed template operation.
Updated documentation.

23 October 2015
MetaTrader 5 Platform Update Build 1200: Tick History and Direct Payment for Services

Terminal

  1. Added ability to work with tick history in the Market Watch. Previously, a tick chart showed only the history collected in the terminal during its operation. Now, you can access the entire tick history on the trade server. Disable auto scroll and start scrolling a tick chart back in time using your mouse to download missing history from the trade server the same way it is done for common price charts. The new feature will be useful for traders who want to get the most detailed price charts.



    Use the CopyTicks() function to receive deeper tick history. It has been modified so that it requests missing history and downloads it if the latter is present on the trade server.

  2. Added an icon for quick opening/closing the Depth of Market. The icon is located near the One-Click Trading panel on the chart. You can also use the new hotkey Alt+B. The hotkey also works in the Market Watch window opening the Depth of Market for a symbol highlighted in the Market Watch.




  3. Information about the PC hardware characteristics and the operating system is now logged to a Journal at the start of the client terminal. Example:
    2015.10.14 14:48:18.486	Data Folder: C:\Program Files\MetaTrader 5
    2015.10.14 14:48:18.486	Windows 7 Professional (x64 based PC), IE 11.00, UAC, 8 x Intel Core i7  920 @ 2.67GHz, RAM: 8116 / 12277 Mb, HDD: 534262 / 753865 Mb, GMT+03:00
    2015.10.14 14:48:18.486	MetaTrader 5 build 1190 started (MetaQuotes Software Corp.)
  4. Imrpoved working with the symbols in the Market Watch:

    • Added display of the amount of symbols in the Market Watch and the total available amount of symbols on the trade server
    • Added a line for adding a new symbol with the smart selection list
    • The search in the new symbol line is performed not only by a symbol name, but also by its description and international name.




  5. Added support for the economic calendar in different languages.
  6. Added missing country icons to the economic calendar.
  7. Added the hotkey for opening the symbol management window in the Market Watch - Ctrl+U.
  8. Fixed arranging open chart windows according to the Window menu commands.
  9. Fixed an error that occasionally hampered the terminal's ability to find a certificate file when using the enhanced authentication.
  10. Fixed an error that could occasionally lead to a price history synchronization looping.
  11. Fixed nulling StopLoss/TakeProfit levels of a previously opened position after its volume has been increased if a symbol is traded in the Request Execution mode.
  12. Fixed checking the ability to place a sell order in case of a long position on symbols in "Long only" trading mode in the Depth of Market.
  13. Fixed Trailing Stop function operation. In some rare cases, a protective Stop Loss for an open position was moved incorrectly.
  14. The terminal interface has been further adapted for high resolution screens (4K).
  15. Fixed unloading history data as being excessive despite regular appeals to it from MQL5 programs.
  16. Fixed display of some user interface elements when working in Windows 10.
  17. Updated translations of the user interface.

Market

  1. Market: Operation with the product database in the MQL5 Market has been revised and optimized.
  2. Market: Purchasing without an MQL5.community account has been disabled for terminals on VPS. The purchase now requires specification of an MQL5.community account in the terminal setting: Tools - Options - Community.
  3. Market: Added direct product purchasing using UnionPay.
  4. Market: Enhanced logging when purchasing products in MQL5 Market.
  5. Hosting: Added managing the virtual hosting (except for migration) when working in the 32-bit version of the client terminal.


Virtual Hosting and Signals

  1. Payments for Virtual Hosting and Signal subscriptions can now be transferred straight from payment systems. To pay for hosting services, users don't need to log in to the MQL5.community account and add money to it. A payment for a service can now be transferred straight from the platform using one of the available payment systems.



    Select one of the available systems and make an online money transfer:




    Similarly, a payment for a trading signal subscription can be made straight from the terminal via a payment system.




    The required amount will be transferred to your MQL5.community account first, from which a payment for the service will be made. Thus, you maintain a clear and unified history of rented virtual hosting platforms and signal subscriptions and can easily access and review all your payments for the MQL5.community services.
  2. Added managing the virtual hosting (except for migration) when working in the 32-bit version of the client terminal.
  3. Fixed migration of FTP export settings to the virtual hosting regardless of the permission to publish reports via FTP.

MQL5

  1. Enabled a new optimizing compiler. Execution of programs has been accelerated up to 5 times on 64-bit platofrms. MQL5 programs should be re-compiled in the last MetaEditor version.
  2. Extended MqlTick structure format. Now, it passes the time of a tick arrival in milliseconds, as well as flags to determine which tick parameter has been changed.
    struct MqlTick
      {
       datetime     time;          // Time of a price last update
       double       bid;           // Current Bid price
       double       ask;           // Current Ask price
       double       last;          // Current Last price
       ulong        volume;        // Volume for the current Last price
       long         time_msc;      // Time of a price last update in milliseconds
       uint         flags;         // Tick flags
      };
    The parameters of each tick are filled in regardless of whether there are changes compared to the previous tick. Thus, it is possible to find out a correct price for any moment in the past without the need to search for previous values at the tick history. For example, even if only a Bid price changes during a tick arrival, the structure still contains other parameters as well, including the previous Ask price, volume, etc. You can analyze the tick flags to find out what data have been changed exactly:

    • TICK_FLAG_BID - a tick has changed a Bid price
    • TICK_FLAG_ASK  - a tick has changed an Ask price
    • TICK_FLAG_LAST - a tick has changed the last deal price
    • TICK_FLAG_VOLUME - a tick has changed a volume
    • TICK_FLAG_BUY - a tick is a result of a buy deal
    • TICK_FLAG_SELL - a tick is a result of a sell deal

    The MqlTick structure is used in two methods:

    • CopyTicks - method does not support the old format of the structure. Previously compiled EX5 files using the old tick format will return the error 4006 (ERR_MQL_INVALID_ARRAY) when calling the CopyTicks function.
    • SymbolInfoTick - method supports both old and new structure format.

  3. Added class templates allowing you to create parametrized classes like in C++. That enables even greater abstraction and ability to use the same code for working with objects of different classes in a uniform manner. Example of use:
    //+------------------------------------------------------------------+
    //|                                                    TemplTest.mq5 |
    //|                        Copyright 2015, MetaQuotes Software Corp. |
    //|                                             https://www.mql5.com |
    //+------------------------------------------------------------------+
    #property copyright "Copyright 2015, MetaQuotes Software Corp."
    #property link      "https://www.mql5.com"
    #property version   "1.00"
    //+------------------------------------------------------------------+
    //| Declare a template class                                         |
    //+------------------------------------------------------------------+
    template<typename T>
    class TArray
      {
    protected:
       T                 m_data[];
    
    public:
    
       bool              Append(T item)
         {
          int new_size=ArraySize(m_data)+1;
          int reserve =(new_size/2+15)&~15;
          //---
          if(ArrayResize(m_data,new_size,reserve)!=new_size)
             return(false);
          //---
          m_data[new_size-1]=item;
          return(true);
         }
       T                 operator[](int index)
         {
          static T invalid_index;
          //---
          if(index<0 || index>=ArraySize(m_data))
             return(invalid_index);
          //---
          return(m_data[index]);
         }   
      };
    //+------------------------------------------------------------------+
    //| Template class of a pointer array. In the destructor, it deletes |
    //| the objects, the pointers to which were stored in the array.     |
    //|                                                                  |
    //| Please note the inheritance from the TArray template class       |
    //+------------------------------------------------------------------+
    template<typename T>
    class TArrayPtr : public TArray<T *>
      {
    public:
       void             ~TArrayPtr()
         {
          for(int n=0,count=ArraySize(m_data);n<count;n++)
             if(CheckPointer(m_data[n])==POINTER_DYNAMIC)
                delete m_data[n];
         }
      };
    //+--------------------------------------------------------------------------+
    //| Declare the class. Pointers to its objects will be stored in the array   |
    //+--------------------------------------------------------------------------+
    class CFoo
      {
       int               m_x;
    public:
                         CFoo(int x):m_x(x) { }
       int               X(void) const { return(m_x); }
      };
    //+------------------------------------------------------------------+
    //|                                                                  |
    //+------------------------------------------------------------------+
    TArray<int>     ExtIntArray;   // instantiate TArray (specialize TArray by the int type)
    TArray<double>  ExtDblArray;   // instantiate TArray (specialize TArray by the double type)
    TArrayPtr<CFoo> ExtPtrArray;   // instantiate TArrayPtr (specialize TArrayPtr by the CFoo type)
    //+------------------------------------------------------------------+
    //| Script program start function                                    |
    //+------------------------------------------------------------------+
    void OnStart()
      {
    //--- fill arrays with data
       for(int i=0;i<10;i++)
         {
          int integer=i+10;
          ExtIntArray.Append(integer);
          
          double dbl=i+20.0;
          ExtDblArray.Append(dbl);
          
          CFoo *ptr=new CFoo(i+30);
          ExtPtrArray.Append(ptr);
         }
    //--- output the array contents
       string str="Int:";
       for(int i=0;i<10;i++)
          str+=" "+(string)ExtIntArray[i];      
       Print(str);   
       str="Dbl:";
       for(int i=0;i<10;i++)
          str+=" "+DoubleToString(ExtDblArray[i],1);
       Print(str);   
       str="Ptr:";
       for(int i=0;i<10;i++)
          str+=" "+(string)ExtPtrArray[i].X();      
       Print(str);
    //--- CFoo objects created via new should not be deleted, since they are deleted in the TArrayPtr<CFoo> object destructor  
      }
    Execution result:
    TemplTest (EURUSD,H1)    Int: 10 11 12 13 14 15 16 17 18 19
    TemplTest (EURUSD,H1)    Dbl: 20.0 21.0 22.0 23.0 24.0 25.0 26.0 27.0 28.0 29.0
    TemplTest (EURUSD,H1)    Ptr: 30 31 32 33 34 35 36 37 38 39

  4. New operations * and & for receiving a variable by reference and receiving a reference to a variable.
  5. Added the overloaded form of the ObjectsDeleteAll function - delete all objects of a specified type by a name prefix in a chart subwindow.
    int  ObjectsDeleteAll(
       long           chart_id,   // chart ID
       const string     prefix,   // object name prefix
       int       sub_window=-1,   // window index
       int      object_type=-1    // object type for deletion
       );

  6. Fixed the ObjectGetValueByTime function operation. Previously, an incorrect price value by a chart time could sometimes be returned (for example, for a horizontal trend line).
  7. Fixed operation of the Copy* functions in the absence of historical data on the server. Previously, such cases caused delays of 30-50 seconds before returning control.
  8. Added a few improvements to the MQL5 Standard Library.
  9. Translated the Standard Library documentation into German, French, Chinese, Turkish, Spanish and Portuguese.
  10. Added MQL5 documentation in Japanese.

Tester

  1. The process of selecting programs to run in the Strategy Tester has become much easier. The list is displayed now as a tree in accordance with the directories in which Expert Advisors and indicators are stored.




  2. Brought display of some indicators during a visualized test in line with the client terminal.
  3. Fixed setting a leverage and a chart timeframe while debugging MQL5 programs via the strategy tester.
  4. Fixed debugging indicators when testing on history.
Fixed errors reported in crash logs.

Updated documentation.


17 September 2015
MetaTrader 5 iPhone build 1167
  • Improved convenience of analytical objects. They only appear on the current chart now. Display on other symbols can be enabled in object settings. To optimize chart area, enable object display only for the timeframes you need.
  • Turn on the display of higher timeframe borders on the current chart by enabling period separators.
  • iOS 9 compatibility improved.
28 August 2015
MetaTrader 5 iPhone Build 1165
  • Improved news section. Select news categories to follow what is interesting for you. Add the news items you like to Favorites to quickly access them wherever you need. Search news by headlines.
  • In the iPhone version trades can now be executed from a chart at a single tap - turn the device into a horizontal position and open a quick trade panel.
  • MetaTrader 5 iOS build 1165

  • Added an option for closing positions of Collateral instruments, which allows converting the corresponding assets into the deposit currency.
  • Various bug fixes and improvements.
26 August 2015
MetaTrader 5 Android build 1164
  1. Added 24 new graphic objects for technical analysis: lines, channels, Gann and Fibonacci tools, Elliott Waves and geometric shapes.

    New MetaTrader 5 Android: 24 Analytical Objects and OTP Two-Factor Authentication

  2. Added support of two factor authentication (One-time password, OTP) for connecting to a trading account
  3. Various bug fixes and improvements
24 June 2015
MetaTrader 5 Android build 1130
  1. Added internal mail system for contacting broker's support team
  2. Added ability to send logs to the application developer's support team
  3. Various bug fixes and improvements

Read whole news text here.

3 June 2015
MetaTrader 5 build 622: Faster and Simpler Purchase of Robots from the Market

Now, you can buy any Market application in a single step directly from your MetaTrader 4/5 terminal without registration. Simply click Buy and select the preferred payment method.


Then you will be redirected to the payment system web page to complete your purchase. PayPal, WebMoney, Neteller or a bank card - you can choose how to pay for your purchases from the store of ready-made robots and indicators.


After making a purchase, we still recommend that you register an account on MQL5.community, so that your purchased product is automatically linked to your account. An MQL5 account enables you to update the product and install it on multiple computers. Besides, an MQL5.community account gives you access to a plethora of other services for the MetaTrader platforms such as trading signals for copying deals of successful traders, virtual hosting for continuous operation of your applications and Freelance for ordering unique robots from developers.

Now, you know the quickest and easiest way to obtain a trading robot. More than 5 000 various MetaTrader applications are already waiting for you in the Market - simply choose and buy!


3 June 2015
MetaTrader 5 iPhone build 1127
  • Added support for a special type of non-tradable instruments, which can be used as the client's assets to provide the required margin for open positions of other instruments. Such assets are displayed as open positions. They increase the free margin amount, thus increasing the volumes of allowable trade operations on the account.
  • New interface language: Hindi.
  • Various bug fixes and improvements.
22 May 2015
MetaTrader 5 Platform Update Build 1150: Easy Purchase from Market, Debugging on History, Time&Sales of Transactions

Market

  1. We are introducing a new mechanism of "direct" purchasing. Purchasing a trading robot or an indicator from the Market is now even easier, and you do not even need an MQL5.community account.

    One-Step Purchase
    A user doesn't need to log in to an MQL5.community account and add money to it. A payment for a product can now be made straight from the platform using one of the available payment systems. To maintain a clear and unified history of purchases from the Market, the required amount will be first transfered to your MQL5.community account, from which a payment for the product will be made.

    You can easily access and review all your payments from your MQL5.community Profile.




    Purchase without Registration
    A product from the Market can be purchased without an MQL5.community account. Click "Buy" and pay for the product using one of the available payment systems.



    Then you will be redirected to the payment system web page to complete your purchase.



    After that, we strongly recommend you to register an account on MQL5.community, and your purchase will be automatically linked to it. This enables you to update the product and install it on multiple computers.

MetaEditor

  1. New features allow to debug Expert Advisors and indicators on history prices. In the older versions debugging required live real time charts.

    Now any program can be tested on required history data. Debugging runs in the visual testing mode in the Strategy Tester. An application is executed on a chart with an emulated sequence of ticks in the tester.

    Configure the debugging parameters in the MetaEditor settings: symbol, timeframe, interval, execution mode, tick generation mode, initial deposit and leverage. These parameters will be applied for visual testing.



    Set the breakpoints in the code, and then start the debugging using historical prices.



    This will initiate visual testing and the debugging process.



Virtual Hosting

  1. Multiple improvements and fixes have been implemented in the Virtual Hosting service.

    The major changes apply to operation in Wine on computers running Linux and Mac OS. All the functions are available for allocated virtual servers in Wine, including migration, performance monitoring and logs.


    The operation of the Log has also changed. If a user requests too many records, then only part of the first logs for the specified period will be downloaded. This prevents performance degradation resulting from large logs. If you need to download further logs, you no longer need to change the requested period. Simply select the last row in the log viewer window and press PgDn.




Terminal

  1. Added support for a special type of non-tradable assets, which can be used as client's assets to provide the required margin for open positions of other instruments. For example, a certain amount of gold in physical form can be available on a trader's account, which can be used as a margin (collateral) for open positions.

    Such assets are displayed as open positions. Their value is calculated by the formula: Contract size * Lots * Market Price * Liquidity Rate.

    Liquidity Rate here means the share of the asset that a broker allows to use for the margin.


    The Assets are added to the client's Equity and increase Free Margin, thus increasing the volumes of allowable trade operations on the account.

    Thus, it is now possible to open accounts with various margin types.


    In the example above, a trader has 1 ounce of gold having the current market value of 1 210.56 USD. This value is added to the equity and the free margin allowing the trader to continue trading even in case of a zero balance.

  2. A new Depth of Market with a tick chart and the Time&Sales data of trades.

    A tick chart of exchange instruments with real transaction prices is now displayed in the Depth of Market. All transactions conducted on the Exchange are plotted on this chart:

    • Red circles - Sell transactions
    • Blue circles - Buy transactions
    • Green circles - the direction of the transaction is undefined. It is used when the exchange does not transmit the direction of a transaction. In this case, the direction is determined based on the price of the transaction as compared to prices bid and ask. A Buy transaction is that executed at the ask price or above, a Sell transaction is executed at the bid price or lower. The direction is undefined, if the price of the transaction is between the bid and the ask.

    The larger the circle, the greater is the volume of the transaction. Transaction volumes are also shown as a histogram below the tick chart.



    At the top and bottom of the histogram, the total volumes of the current Buy and Sell offers are shown.

  3. The symbol selection dialog box now contains a column showing the symbol expiration date. Additionally, expired instruments can be hidden from the list. Expired contracts are automatically replaced with active ones.



    All expired symbols are hidden to preserve a more compact display. This is particularly useful when working on the futures market. A non-relevant symbol is the expired one, which is defined by the "Last trade" parameter. This date is specified in the "Expiration" column. To see all the symbols, click "Show expired contracts".
    The list of symbols is automatically sorted for a more convenient display:

    • first listed are the symbols without the expiration date
    • they are followed by the symbols with an expiration date starting with the nearest date
    • then expired symbols are shown starting with the last expired one
    • other symbols sorted alphabetically

    Option "Auto remove expired" in the context menu allows to replace expired symbols with active ones in the "Market Watch" window.



    After terminal restart, expired symbols are hidden, and active ones are added instead. For example, the expired futures contract LKOH 3.15 will be replaced by the next contact of the same underlying asset LKOH 6.15.

    Symbols in the appropriate open charts are also replaced, provided there are no running Expert Advisors on them.

  4. Fixed updating of trade button states in the Depth Of Market window depending on whether there are any positions, and on the permission to open only long positions. If there are no positions, the Close button is inactive. If opening short positions is not allowed, the Sell button is inactive.
  5. The terminal interface has been further adapted for high resolution screens (4K).
  6. Fixed verification of the volume of a closed position in the Request Execution mode, in case a deal volume is less than the minimum allowable value.
  7. Fixed an error that could occasionally lead to launch of multiple terminal instances from one directory.
  8. Added support and automatic filtering of the economic calendar in different languages. Filtering is performed in accordance with the language of the terminal interface.
  9. The Log Viewer now features search through the currently displayed logs.



    It searches for a word/phrase in the displayed list of logs.
  10. Added Thai translation of the client terminal.
  11. Updated translation of the client terminal into Hindi.

MQL5

  1. New function GetMicrosecondCount returns the number of microseconds that have passed since the start of the MQL5 program:
    ulong  GetMicrosecondCount();
    This function can be used to profile program execution and identify "bottlenecks".

  2. New chart property CL_BUFFER_SIZE in the ENUM_OPENCL_PROPERTY_INTEGER enumeration - it returns the actual size of the OpenCL buffer in bytes. The property can be received via the CLGetInfoInteger function.
  3. An error notification in the WebRequest function has been modified. If an error occurs, the 'result' array will contain the description of the error.
  4. The ArraySort, ArrayBsearch, ArrayMinimum and ArrayMaximum sort and search functions are now able to work with multidimensional arrays. Sort and search are performed only by the first (zero) array index. Previously, these functions worked only with one-dimensional arrays.
  5. Fixed some bugs in the compilation of macros.

Tester

  1. Some improvements and bug fixes in the operation of the visual testing. The tester now provides a smoother control of testing speed using the toolbar.

Fixed errors reported in crash logs.

Updated documentation.

The update is available through the LiveUpdate system.

1 May 2015
MetaTrader 5 iPhone build 1105
  • Added support for 64 bit processors.
  • Optimized internal chat: improved synchronization and renewed design.
  • Added ability to create an anonymous demo-account for immediate start of operation. The account does not require registration data and can be opened in one tap.
  • Improved working with news: automatic language filtering and improved representation of news.
  • Increased speed of trade request sending.
  • Added ability to display the Ask line on chart.
  • Added special category for notifications from virtual hosting.
  • Added Thai, Vietnamese, Malay and Ukrainian translations of user interface.
  • Numerous improvements and enhancements.
12345678910111213