New MetaTrader 5 Platform build 4040: Improvements and fixes

[MetaQuotes]

The MetaTrader 5 platform update will be released on Friday, October 20, 2023. This version provides improvements to the new trading report and the Web Terminal.

MetaTrader 5 Client Terminal

1. Terminal: New trading report improvements. Fixed display of the first value on the growth graph and drawdown calculations.

   
   

   
   
2. Terminal: When opening accounts, traders receive several messages through the internal email system. They provide credentials and useful information about the platform capabilities and built-in services. We have updated and enhanced these emails, translated them into 50 languages, and completely updated the design.
   
3. Terminal: Optimized account deposit and withdrawal pages.
4. Terminal: Fixed volume change error when placing a new order. With some combinations of trading instrument settings, the field was not available for editing.
5. Terminal: Fixed display of broker agreement links in the demo account opening dialog.
6. Terminal: Updated user interface translations.
7. MQL5: Fixed an error that could cause the MQL5 program to crash at startup under certain conditions.
   
   

MetaTrader 5 Web Terminal

1. Fixed display of Stop Loss and Take Profit values in trading history.
2. Enhanced logging. New log messages display information on successful and failed connections.
3. Fixed context menu operation in the Market Watch.
4. Fixed display of notifications about operation results when trading from the Depth of Market.
5. Fixed error which caused the indicator subwindow to be removed from the chart when calling the trading dialog.
6. Fixed on-chart dragging of trading levels displayed on top of analytical objects.
   
   

The update will be available through the Live Update system.

[Roodie]

Draw trendline by angle has bug when changing timeframe.

[Vladislav Boyko]

Is this display of the signature correct?

(Ctrl+Shift+Space)

[Vladislav Boyko]

Vladislav Boyko #:
Is this display of the signature correct?

It looks like the <Ctrl+Shift+Space> is displaying an incorrect signature.

<Ctrl+Space>:

<Ctrl+Shift+Space>:

---

class Foo
  {
public:
   int i;
   const Foo* method();
  };

const Foo* Foo::method(void)
  {
   return(NULL);
  }

void OnStart()
  {
   Foo obj;
   const Foo* ptr = obj.method();
  }

[Dr Matthias Hammelsbeck]

If I open three long positions with 0.1 lots in USDJPY and using a netting account, I get one position with 0.3 lots (that is completely ok) and an average price which is not correctly displayed: 6 digits after the comma instead of 3:

 

[Fernando Carreiro]

@Dr Matthias Hammelsbeck #: If I open three long positions with 0.1 lots in USDJPY and using a netting account, I get one position with 0.3 lots (that is completely ok) and an average price which is not correctly displayed: 6 digits after the comma instead of 3:

Correctly speaking, the Net Mean Open Price for a basket of orders can easily be a value that does not align to the tick/point size.

However, I don't know if it was expressed (displayed) in previous builds in this way. If you are stating that in previous builds it was rounded to the nearest tick or point size, I cannot argue that as I did not notice.

But internally, the correct value will usually not align to a tick/point size because of how the Net Mean Open Price is calculated.

If in this build, it is now displayed in this way, then I personally would argue that to be a very good thing, so as to know the real Net Mean Open Price.

[Dr Matthias Hammelsbeck]

Fernando Carreiro #:

Correctly speaking, the Net Mean Open Price for a basket of orders can easily be a value that does not align to the tick/point size.

However, I don't know if it was expressed (displayed) in previous builds in this way. If you are stating that in previous builds it was rounded to the nearest tick or point size, I cannot argue that as I did not notice.

But internally, the correct value will usually not align to a tick/point size because of how the Net Mean Open Price is calculated.

If in this build, it is now displayed in this way, then I personally would argue that to be a very good thing, so as to know the real Net Mean Open Price.

I understand what you mean. But in some cases (eg if the volume is divided by 3) you never can display the correct value. Why 6 digits? That seems to me a little bit arbitrary.

[Fernando Carreiro]

I would like to hereby confirm a bug in the Strategy Tester's forwarding testing, as discovered and described by the user tanner gilliland in the following 4 topics ...

• Can anyone see if they can reproduce a bug on their computer? It wont take long.
• Is there a way to run or rerun forward tests with the same inputs as a previous backtest?
• Why would the number of passes in the strategy tester determine whether a bug happens or not.
• How can I see what exactly went wrong when a forward optimization pass fails?

I personally run the test offered by the user to reproduce the issue and confirmed his findings.

My complete testing procedure and results, including log files can be found on the following consecutive posts:

• https://www.mql5.com/en/forum/457425#comment_50704805
• https://www.mql5.com/en/forum/457425#comment_50704819
• https://www.mql5.com/en/forum/457425#comment_50704852
• https://www.mql5.com/en/forum/457425#comment_50704895
• https://www.mql5.com/en/forum/457425#comment_50704950

Please note, that credit for discovering this bug goes to the user tanner gilliland!

[Fernando Carreiro]

Fernando Carreiro #:

I would like to hereby confirm a bug in the Strategy Tester's forwarding testing, as discovered and described by the user tanner gilliland in the following 4 topics ...

• Can anyone see if they can reproduce a bug on their computer? It wont take long.
• Is there a way to run or rerun forward tests with the same inputs as a previous backtest?
• Why would the number of passes in the strategy tester determine whether a bug happens or not.
• How can I see what exactly went wrong when a forward optimization pass fails?

I personally run the test offered by the user to reproduce the issue and confirmed his findings.

My complete testing procedure and results, including log files can be found on the following consecutive posts:

• https://www.mql5.com/en/forum/457425#comment_50704805
• https://www.mql5.com/en/forum/457425#comment_50704819
• https://www.mql5.com/en/forum/457425#comment_50704852
• https://www.mql5.com/en/forum/457425#comment_50704895
• https://www.mql5.com/en/forum/457425#comment_50704950

Please note, that credit for discovering this bug goes to the user tanner gilliland!

Follow-up ...

It seems that this has been a bug for a long time, at list sice 2020 ... tester got "xx pases not processed and returned to task queue" warning

[investorwat]

The Balance/Equity graph in MT5 backtest report is wrong in the generated HTML. Equity curve is missed in the generated HTML.

The Balance/Equity graph is correct in MT5Terminal.

Please see the pictures attached.

[Miguel Angel Vico Alba]

Comments that do not relate to this topic, have been moved to "I can't see the reports in Windows Server 2019".