New MetaTrader 4 Client Terminal 387 and MetaTrader 4 Data Center build 387 - page 2
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
We have specifically started beta testing the new build to test it before releasing the full version to all brokers. MetaTrader 4 will be officially released in March.
Please report any problems you notice in this thread. It is very desirable to attach more details.
If there are problems with the indicators, please send their full code to stringo AT metaquotes.net for verification. After the checks the code will be removed.
Please report any problems you notice in this thread. It would be very much appreciated if more details could be attached.
1) Very much please fix "sticking" Digits when switching from 4 digits to 5 and back https://www.mql5.com/ru/forum/119283 and https://www.mql5.com/ru/forum/130629
2) And also to make definition of timezone of server through MarketInfo https://www.mql5.com/ru/forum/123222/page5#258937
3) And it would be cool to have the function IsAccountReady, which would return true if the terminal has received all of its historical (since the very first) and open orders and the most important thing - that the history for the current symbol/period has already been downloaded and there will be NO new historical ticks https://www.mql5.com/ru/forum/128436
4) quite a small thing - in the tester, they need to somehow mark places where data from low-end timeframes started to be used. For example, when you open a chart after a chart chart is drawn not only deals but vertical lines with the names "Using-M5" or something like that and they should also be displayed in the text as a result of testing.
Unfortunately, we will only be correcting bugs in MT4 with the 387 build.
Most likely there will be the last updates to the MetaTrader 4 platform in March.
I remember a message from METAQUOTES,
that Datacenter has ceased to exist and is no longer supported
has the situation changed ?
The Datacenter has long been used only by the DC.
It has ceased to exist for mere mortals only.
can we focus on this product ?
This message is for those who continue to use the old versions.
Essentially traders do not need datacentres, as datacentres have moved to mass maintenance mode (for trading servers) and no longer save traffic for a small number of users.
Unfortunately, we will only be correcting bugs in MT4 with the 387 build.
Most likely in March there will be the last updates to the MetaTrader 4 platform.
What does this mean?
Will MT4 cease to exist?
What does this mean?
Will MT4 cease to exist?
What does that mean?
mt4 will cease to exist?
has already been said many times
It won't...
I can only assume it's just - they'll bring it to some kind of a state
and then abandoned... so there will be little or no refinement...
it means that if they find a glaring error, they'll fix it.
but apparently they won't accept suggestions for improvements
So everyone will have to rewrite ALL optimised indicators! Down with optimisation...
Hopefully point 6 was made in error. And the final version won't have this fix.
Where is the exact explanation of what this point means?
I could interpret it as elimination of my mistake: https://www.mql5.com/ru/forum/2909/page2#comment_42005
in this new build it is now gone...
here's the EA that tracks this has been standing from the beginning of Monday until now, and FULL REINSTALLATION for all that time (read: internet problems, broken connection, cut bars) has only been there:
GetTickCount;LastBars;Bars;LastIndicatorCounted;IndicatorCounted
7452963;65000;65000;0;0
60276415;65000;65394;0;0
64656829;65394;65467;0;0
64659497;65467;65467;0;0
68008947;65467;65523;0;0
86581319;65523;65832;0;0
86602223;65832;65833;0;0
96912766;65833;66005;0;0
96959067;66005;66005;0;0
113377985;66005;66279;0;0
125810719;66279;66487;0;0
140239547;66487;66728;0;0
140257176;66728;66728;0;0
171526406;66728;67122;0;0
179198192;67122;67122;0;0
183412824;67122;67192;0;0
214761880;67192;67587;0;0
17 times in 57 hours of continuous operation
Where's the problem then???????
Addendum: appended full log