Big changes for MT4, in a few weeks - page 64
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
Build 565 - problems described here https://www.mql5.com/en/forum/183353/page40 seem to be solved. Problems with wrong object display also seem to be solved. Problems described here https://www.mql5.com/en/forum/183353/page41 still the same
Build 565 - problems described here https://www.mql5.com/en/forum/183353/page40 seem to be solved. Problems with wrong object display also seem to be solved. Problems described here https://www.mql5.com/en/forum/183353/page41 still the same
At least some good news.
Now we have to see when will they remove all the bugs
It is obvious that they are planning to launch it soon. We shall see when we are forced to use it on everyday basis what has been done in debugging and if that is going to allow us a normal trading. Also, we shall see what are brokers going to do (I have seen cases when some brokers refused to use some builds because they were not safe for their users - Alpari did it a couple of times that I know of).
Build 566. Issues from this post https://www.mql5.com/en/forum/general still the same. One new major issue : if you have a custom indicator that should work on a main chart (not in a sub-window) already attached to a chart and you want to attach another instance to the chart, you can not. Build 566 allows only one instance of the same custom indicator on te main chart (it seems that it confuses EAs and indicators)
Build 566. Issues from this post https://www.mql5.com/en/forum/general still the same. One new major issue : if you have a custom indicator that should work on a main chart (not in a sub-window) already attached to a chart and you want to attach another instance to the chart, you can not. Build 566 allows only one instance of the same custom indicator on te main chart (it seems that it confuses EAs and indicators)
One step forward two steps back?
Here is a new year. Happy new year to metaquotes - hope that I will not have to wish them a happy new year on this same thread again
One step forward two steps back? Here is a new year. Happy new year to metaquotes - hope that I will not have to wish them a happy new year on this same thread again
Here is one little thing that will probably be common in new metatrader 4. This is a fully functional adaptive T3 rainbow indicator. Attach it to the chart and it will work OK. Now rename it (to anything) and try to run it. That is the mildest thing that can happen when there is no decompilation and when the usual practice of renaming is attempted (don't worry it will not delete anything - this one is benign
). But I am sure that some people are not going to like things like these ...
_______________________
PS: the indicator will not work with the current regular metatrader 4 (build 509). This version will work only with the new metatrader 4
You mean that the time of code sharing is closing to end?
That would not be good
People, some things that are specific for metatrader 5 are not going to be implemented in metatrader 4 at all. According to one answer from renat the main reason why metatrader 4 is upgraded is signals market, not something else (like improvement of the trading platform, good forbid)
Build 566. Issues from this post https://www.mql5.com/en/forum/general still the same. One new major issue : if you have a custom indicator that should work on a main chart (not in a sub-window) already attached to a chart and you want to attach another instance to the chart, you can not. Build 566 allows only one instance of the same custom indicator on te main chart (it seems that it confuses EAs and indicators)
Hi mladen,
I noticed this issue on build 560 when I tried to load several custom indicators onto the same chart, the only way around it is to change one input on the first indicator loaded and from that point as long as you load each proceeding indicator with different inputs it allows you to load more instances of the same indicator. If the first indicator is loaded with no input changes then it will not allow you to load any more of the same custom indicator. Obviously not an ideal situation however it can be got around for what its worth.
Hi mladen,
I noticed this issue on build 560 when I tried to load several custom indicators onto the same chart, the only way around it is to change one input on the first indicator loaded and from that point as long as you load each proceeding indicator with different inputs it allows you to load more instances of the same indicator. If the first indicator is loaded with no input changes then it will not allow you to load any more of the same custom indicator. Obviously not an ideal situation however it can be got around for what its worth.
It's no different than 509 which has the same "problem". I think it may be intentional.