Bug reports for MT4 build 600+

As Metaquotes does not seem to respond much to reports of problems with the new version of MT4 in their forums, I'll post them here instead. Feel free to post about any bugs, inconsistencies, idiosyncrasies etc you have encountered.

Two colors for icons in navigator used to display three different states (Build 604).

Yellow - 'Working indicator' with source code available.
Grey - 'Working indicator' without source code.
Grey - 'Not working indicator' with source code available. Does not compile under MT4.5 but did compile under MT4 and had a previously compiled ex4.

It should be possible to use more than 2 colors. No?

Custom Indicators in sub-folders that call other custom indicators also in the sub-folder take very long to load (Build 604).

If you create a sub-folder for a set of indicators and any of those indicators use iCustom to call other indicators also in the sub-folder, load times for the indicator using iCustom will be very long. Ie, you cannot just move a set of indicators into a sub-folder without any penalties.

Having the source code of indicators that are not compatible with build 600+ in the '..\MQL4\' folder may lead to said indicators ceasing to work at some time in the future (Build 604).

If for some reason, MT4 decides to compile the indicators, the compilation will fail and the indicators will not work any more as the old ex4 file will have been deleted. This seems to be the most common issue of indicators not working after the upgrade from build 509 to build 600+.

Workaround:
Remove the source files for all indicators you know will not compile under build 600+ from the '..\MQL4\' folder.

Hi Zaphod,
There was until the last build 604 an issue with multi line comments and that appears to have been resolved however it still is a problem with the Alerts text. Build 604 still basically ignores the "\n" line break in the code although all other comments such as comments for EAs and on chart indicator comments are now working as they should.

See the 2 examples build 604 and build 509.

Build 604


Build 509

Alert() overrides Playsound() in indicators (Build 600+ and Build 509-)

If one calls PlaySound() just before or after Alert(), the Alert sound overides the PlaySound sound. Therefore it is not possible to have popup alerts with varying custom sounds.

In EA's and scripts, it PlaySound() that overides Alert() which is the way one would expect it to work.

Workaround:
Disable the system sound for the Alert Dialog: Options Dialog, Events Tab. However this means than other popup alerts that do not use PlaySound() will not sound at all.

Dropdown list for enumerated types is in reverse order in the parameter dialog (Build 605)

This is an old issue. Previously reported, seemingly ignored by Metakvotov.

MTF indicator using Array functions uses up excessive amounts of memory (Build 605)

This indicator TDI-MTF-zz.mq4 that works normally in build 509- uses up 400k of RAM per instance in build 600+. If you have 4 of these babies on each chart you can only have 2 charts open before your run out of memory on computer with a 4Gig RAM. Guess it is an improvement. It did not work at all in some of the 'beta' versions. Previously reported, seemingly ignored by Metakvotov.

This is a nice one. After a reconnect the init() procedure is not called any longer leaving all init() dependable variables initialized by zero.

A reconfiguration request does nothing.



Restart of the platform is required to let the init() run again.

This is how init() normally logs in this EA.


Edit: They know it already ...

Hey guys, My latest MT4 is not giving me alerts in a popup window. It is playing sound though.

Can anybody guess when the B600 was stopped according to the process explorer?



For comparison: This is the B509 on the live account.



MetaTrader4 in the current state renders a virtual machine (like in a VPS) nearly unusable.
It's sluggish and buggy.

This poor guy had the patience to be lied upon by the MetaQuotes service desk for six weeks? This is what I call a good commercial support.


(source: http://forum.mql4.com/60578)

Synopsis: Backwards compatibility of old *.ex4? My a...nkles.

Build 600:

1. MQL4\Include\Controls\SpinEdit.mqh - one function for max value returns min value instead.


2. The custom graphical panels (http://www.mql5.com/en/articles/345) attached to a chart disappear after I restart the program.

This is why I never use their standard libraries. The are hot and untested and if you find a bug, you cannot fix it, because it gets overwritten in the next update.

Just for the records: I've put the whole experts/ structure into an SVN(*) where the workspace is on windows and the repository resides on a Linux machine which has nothing to do with MT4.

In this way they always can update their libs and I always can

a) merge the differences by a graphic interface
b) rollback their changes if they're really that borken.

In either way - MQ has proven that they'd better not controlled the sources on my machine...

(*) http://tortoisesvn.net/downloads.html

Excellent approach. I have been thinking about a simple script, that would scratch anything from the include folder (files and folders), if it did not belong to the SVN repository. Yet no clue how to do it.

Hi all, here is what I have found so far while porting my EA to MQL5 (Metatrader Build 610)

I have actually both platforms (Build 509 and 610) running in parallel so it was easy for me to compare.

I'm running my tests on the 5 min time-frame. Historical data is from 2008 to 2013 and was exported from build 509 and imported into build 610 so I'm sure I'm using the same data in both builds.

Rewriting the code to be 610 compliant and compiling was without any problem and didn't took major modifications so this was a good surprise but :

1) Strategy tester in 610 is very very slow, going through 6 years of back-test took 9 mins to build 610 when it took less than 1 minute to build 509 !!!

2) The tests results are different ! And thus having the same bars, ticks modeled and modelling quality ! I get different profit, and drawdowns !

3) It's seems that it's impossible to debug using historical data as you need server ticks, so it's impossible to debug during weekends, what a pity !

That's all for now...

hi,xaphod

it was a long ago since you created this indicator,attached below.
i always use this indicator(very useful for me),but it didnt work anymore with mt4 build 610.
would you fix this indicator?
although i only use adr indicator and h1+h4 top n bottom line.
thanks for your kindess.

Alerts are fine in my live platform but neither sound nor screen alerts are working in Strategy Tester.

It appears that as of build 625 (or perhaps bugfix 628?), the company considers the product as ready. So any outstanding issues you may be having are your own problem. Will the next step in the process be to block build 509 clients from connecting to servers?