MQL5 Suggestions - page 3

 
stringo :


3. "May be" means "yes, but not right now" 


Fabulous :-) Great news.

 

Forgot to ask - where did the history center go? I hope that we will still be able to import historical M1 data. 

 
skatt :
It would be handy if EAs could create files in custom subfolders.



is possible to have a programming example of how to add the moving average ? thanks
 

stringo, I've got another question:

 

Will it be possible to simulate periodical cash withdrawal in strategy tester? This seems to be important issue as in real world you consume some of your profits regularly (of course if you have any ;) )...

 

Regards,

 

Enigma71 

 
Enigma71fx   :

stringo, I've got another question:

 

Will it be possible to simulate periodical cash withdrawal in strategy tester? This seems to be important issue as in real world you consume some of your profits regularly (of course if you have any ;) )...

 

Regards,

 

Enigma71 

May be. But I don't know how it should be implemented. It should be separated from EA functionality function

You have direct access to the support and developing team. Ask question with strong arguments please

Happy new year 

 
Hi to all,

I am a novice in the world of TRADING, and at this moment I am experimenting the beta version of metatrader 5, that in my opinion (although not to perceive very much of programming, MQL), seems to be very good. But I only want to give to a suggestion since Metatrader 5 is in experimental phase, think that this is possible and that it would go to benefit a little more Metatrader 5 in the way of visualization of the graphs , a tool as the, PAN Tool and the Area Zoom Tool, I think to be two tools very used by traders, in other softwares and that allow to fast access specify zones of the graph. I leave this suggestion in the hope that the creators of this good software, think and try to incorporate this type of tools, to complement it all the existing others already, in this new Metatrader 5.


My sincereous regards to all
 

stringo:

 

The strong reason is that in real life, you never trade just for trading - you trade to earn profits, which you withdraw (maybe not all of them, but definitely a part of them) from your trading account either to pay your bills or buy yourself a yacht or Porsche ;) I was thinking about being able to predefine subtracting some certain amount of money from your total equity at a certain date while running backtest in the strategy tester (of course with a condition that you are only able to do withdrawal if you have profits = if your total equity is higher then your start equity). In such case, after each withdrawal you would see that the equity line drops sharply by a certain amount, equal to the amount of money you decided to withdraw and the rest of money would be the amount used for the remaining part of backtesting.

Of course if implemented, this should be optional - to run the backtest with withdrawal simulation or without it.

 

You have recently said that you are going to implement some of the features in the future, but not right now - I have an idea for another improvement that might add great value to MetaTrader 5 (not necessarily right now, as you probably already have tight schedule with MT5). It is regarding walk-forward analysis, which is in a sense an improved method of historical testing and optimizing. The basic idea is shown below:

  

/go?link=http://amibroker.com/guide/h_walkforward.html 

 

Regards and a happy new year for you too :)

 

Enigma71 

 

Enigma71,

It's absolutely clear about earning profits. But deposit and withdrawal operations are manual operations. In this case we should implement special functions for testing purposes only

 
stringo :

Enigma71,

It's absolutely clear about earning profits. But deposit and withdrawal operations are manual operations. In this case we should implement special functions for testing purposes only


I understand. And what do you think of this walk-forward testing thing?
 

One small thing about the debugger. I saw the debugger is a special mode that runs similar to forward testing. However, just waiting for some lazy ticks to help testing the darkest corners of the EA is certainly no good. Shouldn't the debugger run inside the strategy tester, that surely, in its huge data history that uses, covers allmost all possible situations and EA functions? 

 
MQL5 Suggestions: static fields and static methods for classes
Reason: