MetaTrader 5 Platform update build 3280: Improvements and fixes based on traders' feedback - page 3

 
fxsaber #:

Error instead of Warning.

According to the Documentation: enum refers to some limited set of data. In this sense, comparison and assignment are not fundamentally different: in both cases there must be either Warning or Error. And the fact that you can compare and you can't assign is nonsense

 

Language must be strict and mixing/auto-enumeration is a very common mistake.

This is why you cannot relax checks and auto-enumeration.

If you want to compare and assign, write an explicit function. The least you need to do is to do it in C style.

 
Renat Fatkhullin #:

Language must be strict and mixing/auto-enumeration is a very common mistake.

This is why you cannot relax checks and auto-enumeration.

If you want to compare and assign, write an explicit function. The last thing you need is to fiddle around in C style.

So it's suggested that we must not allow (Error together with Warning) implicitly comparing different enums.

This is not logical - so it is either programmer's error or we need an explicit conversion to int

 
period converter does not work !!! on 4 !!! in build 1353 and 1355 it does not work log writes but hangs but history file is not written
 
ruslan #:
period converter does not work !!! on 4 !!! in build 1353 and 1355 it does not work log writes but hangs but history file is not written
This thread is for Metatrader 5 (about the latest MT5 build 3280).
Please, repost your question to MT4 thread: MetaTrader 4 platform update build 1353
MetaTrader 4 platform update build 1353
MetaTrader 4 platform update build 1353
  • 2021.12.09
  • www.mql5.com
The MetaTrader 4 platform update will be released on Friday, December 10, 2021...
 
A100 #:

So it is proposed to prohibit (Error together with Warning) implicitly comparing different enum

This is not logical - hence it is either a programming error or we need an explicit conversion to int

Yes, comparisons should also be considered an error instead of a warning.
 
Run debug of this script.
void OnStart()
{
  MqlTick Ticks[];
  ArrayResize(Ticks, 1);
  
  DebugBreak();
}

Add to tracked Ticks[0].asl. The end specifically says l.

Now double click on the highlighted monitored expression.


We get ME (b3280).

Search string:Oshibka 041.

 
Alexandr Gavrilin #:
There are sessions, but brokers are too lazy to write them all down. I have faced with this in Otkritie; the support has referred to the Moscow Stock Exchange and said they could not change the settings. Therefore, my Expert Advisor has been unable to understand when trading is not allowed. I had to prescribe in the code the time for the simulation.

It's not a session, it's a mess. The broker has nothing to do with it!

It is the Exchange that broadcasts the session data.

 
MetaQuotes:

The MetaTrader 5 platform update will be released on Friday, April 29, 2022. The update provides improvements and fixes based on the feedback we have received after the release of build 3270.


The update includes the following changes:

  1. Terminal: Fixed filling of standard Trailing Stop levels in the context menu of open orders and positions.





  2. Terminal: Updated user interface translations.
  3. Fixed errors reported in crash logs.


The update will be available through the Live Update system.

Thank you.

 

Dear developers, please add the possibility for the matrix columns and rows in the right sub-window of the "Tools" window not to be collapsed when the matrix values are updated during debugging.

A simple example (Fig.1). An_MX matrix is created. A couple of clicks opens the first row for viewing values.


Fig.1


If you execute line 15 in the code, all rows and columns will collapse (Fig.2). And to see new values, one has to click on the matrix name again...


Fig.2