Chatter about the MT5 strategy tester - page 4
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
There is one mistake in MT4 tester too
Visualization and optimization are not connected to each other
If you start optimization when visualization is enabled, the terminal hangs.
Although, logically, visualization should not work automatically in the optimization mode.I think that the developers simply do not know how a usable optimizer should look like, would be happy to redesign it, but do not know how.
I already suggested, there are a lot of ace players who can twirl graffobjects as well as jugglers with maces, make a few variants of the tester, as it could look like, the community would judge, correct and choose the most convenient option. And the developers would only have to redo the tester's GUI. And everyone would be happy: the developers wouldn't need to waste time on design and thinking and the community would finally get what it's been wanting for a long time.
As it is... We ask for it, but the developers still don't understand what people want from them.
I think that developers simply do not know how a usable optimizer should look like, would be happy to redesign it, but do not know how.
I already suggested, there are a lot of ace players who can twirl graffobjects as well as jugglers with maces, make a few variants of the tester, as it could look like, the community would judge, correct and choose the most convenient option. And the developers would only have to redesign the tester's GUI. And everyone would be happy: the developers wouldn't need to waste time on design and thinking and the community would finally get what it's been wanting for a long time.
And so... We ask for it, but the developers do not understand what people want from them.
So let's discuss what anyone needs from a tester.
It would be great if the developers participated in the discussion with their 1001 arguments why it can not or should not be done that way.
Maybe it's true, adding one checkbox takes years of development and testing of a new code)))
So let's discuss what anyone needs from a tester.
It would be very nice if developers participated in the discussion with their 1001 arguments why it can't or shouldn't be done that way.
Maybe it's true, adding one checkbox takes years of development and testing of the modified code)))
The problem is that one asks for a checkbox, the other - something else, users' wishes are coming in regularly, but there is no common understanding of what is needed after all, because design and ergonomics is not the same, what to add overloading to standard functions or something like that, GUI is something complete and integrated, details which individually change means spoiling the integrity of users' perception. And that's why a revision, a comprehensive rethinking of the GUI is needed. To do this, we need to create a design and functionality template for the tester in the form of a panel, of course all the functions are dummy.
So, we need to generalize the needs of all users, discard what is reasonable and add what is not.
After all, everyone has his or her own subjective preferences and needs. For example, I don't need all the ticking crap, but everything that deals with the pending orders is very important, while someone does not need pending orders, and important are ticks and everything associated with them)))
And someone may be found and create a layout of all that.
So, it is necessary to generalise the requests of all users, discard what is reasonable and add what is not.
Write out a list of the tester's functionality? - There was no understanding of what a tester should look like, and it won't do any good.
It is necessary to begin to make the layout of the tester in the form of a panel of graphobjects, without that such discussions will remain just discussions and nothing more.
Write out a list of the tester's functionality? - What good would that do? There was no understanding of what a tester should look like, and it won't do any good.
We need to start making the tester's layout in the form of a panel of graphobjects, without that such discussions will remain just discussions and nothing more.
Let's look for someone who can make a layout.
And we'll be asking him to add this and take that away.
Metocwat just need to hire a savvy marketer to explain to them that laziness is the engine of progress!!!
Their success largely depends on how they can meet the challenges of time and buy out the things the end user is too lazy to do)))
No offense, but they probably know better what to do because they built this business, this MQ empire, and they can advise you who to hire and who not to.
But what is interesting, they read the forum carefully, and sort out the right ideas and advice.
Here is a brief outline of everything that is either askew or missing in my personal opinion:
1. the display of the delays.
2. Sketching of objects and indicators on the visual testing chart.
3. Possibility to exclude parameters from genetic algorithm.
4. Testing and optimization agents should not be run with a low priority.
5. A checkbox for optimization mode, which, in its turn, should be automatically reset after optimization completion.
6. Optimizationresults should be saved in full.
7. Separate tabs for test report and test results.
8. It is desirable to move all tabs from the terminal to the tester which relate to testing,
Only one button to call the tester should be left in the terminal.
9. Ability to run testing in parallel with optimization.
10. Stretch the scrolling speed range between the highest speed and the one before it.
11. Ability to include the current day in testing as well.
12. Ability to apply the parameters obtained after the optimization for a test run not only for the current EA, but also for another EA if the parameters are the same.
13. Ability to save the optimization results so that they can be uploaded back later.
14. Although it probably does not belong to the tester, but it is possible to shade a group of parameters depending on a certain parameter.
15. More readable (understandable) history of orders and deals.
I do not want to offend, but perhaps they know better what to do, because they built this business, this MQ empire, and it is rather them who can give advice on who to hire and who not to hire.
But the interesting thing is that they read the forum carefully, and sort out the right ideas and advice.
The main advantage of their platform is the terminal, tester,MetaEditor and language in one package.
If they found someone else with the same platform + some more goodies, the empire may as well go down.
If they had read carefully what people write, they would have implemented hedging in the terminal 10 years ago!!!
Who needs netting? Two stakes players on the stock market? I think the bulk of them are in the forex market.