
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
I don't know if this is the right question.
Is it possible to combine debug and tester? I.e. if I start with F5, the tester doesn't start of course. And if I start the exprrt in the tester, the breakpoints are ignored. Or am I doing something wrong?
I don't know if this is the right question.
Is it possible to combine debugging and a tester?
Not at the moment.
So only in real time on the demo? What about debugging on interesting situations?
I was so excited about the debugger at first, but I'm sliding back to debugging printouts. No other debugging techniques are visible. - Frustrating.
Studying the Expert Advisor supplied as an example, MovingAverage. Everything about it is beautiful. Question on the tester.
This EA analyses the candlestick only on the first tick. I noticed that some situations are slipped without processing. It turns out that a rare candlestick is born from the first tick. Is it a connectivity effect, my glitch or that of the tester?
Apparently, in order to process a candle only at birth, i.e. once, the last processed candle should be stored in a static variable?
P/S/ Just starting to learn the language, hence such tedious questions.
Hello, I am writing an EA to see if I can make it in time for the championship. I wrote some simple code, it uses 2 custom indicators, but the value of these indicators is 0, so the trade is not done.
Lunatic:
This EA analyses a candle only on the first tick. I noticed that some situations slip through without processing. It turns out that a rare candlestick is born from the first tick. Is it a connectivity effect, my glitch or that of the tester?
Apparently, to process a candlestick only at birth, i.e. once, we should store the last processed candlestick in a static variable?
It is better to track the appearance of a new bar by changing the time of the bar, previously storing it in a static variable.
Examples can be found in the article IsNewBar and in the article Limitations and checks in EAs.
The appearance of a new bar is better tracked by changing the time of the bar, having previously saved it in a static variable.
Examples can be found in IsNewBar, and the article Limits and checks in EAs.
Thank you, that's clear.
But here's what I don't understand - how to debug EAs. It is clear that it is not the system that is being tested, but the bugs in the program. For example, it is not clear why the program does not enter a certain branch - why? Do I need to put different debugging stamps, then look for them in the journal, then put other stamps, wait for a certain time until the program is working and then look again in the journal ?
What is the best way to search for program errors?
Hello, I am writing an EA to see if I can make it in time for the championship. I wrote some simple code and used 2 custom indicators, but the values of these indicators are 0 and no trades are executed.
To debug your code I have replaced custom indicators with MA:
And corrected copying of values into array:
Now there are indicator values:
To debug your code I replaced the custom indicators with MA:
And corrected the copying of values into the array:
Now there are indicator values:
So it's all about the indicators? The tester is giving me an error
2010.09.01 19:44:36 Core 1 2010.06.01 00:00:01 Array out of range in 'trend_v3.mq5' (71,9)
2010.09.01 19:44:36 Core 1 2010.06.01 00:00:01 Array out of range in 'trend_v3_5.mq5' (83,9)
To m_a_sim
I think it's more correct to check the handicapability of handles before copying information from the indices. It would also be better to check availability of these data ....