It's true, OnDeinit with control request hasn't been called. Because of the indicator testing. OnDeinit only during debugging
And why during debugging on historical data no ticks are given before test start date? The tester has received them and synchronised them after all. I understand that in the "All ticks" mode the tester cannot generate ticks before the beginning of testing, but in the "Every tick based on real ticks" mode they are present in the history and synchronized (highlighted in red in the log+)! How then to debug the part of the tick indicator that is based on history data? How to get the ticks of bar time[0] in the OnCalculate in the tester?
2019.02.2010:45:28.357 RTS-3.19: symbol to be synchronized
2019.02.2010:45:28.357 RTS-3.19: symbol synchronized, 3864 bytes of symbol info received
2019.02.2010:45:28.365 RTS-3.19: history synchronization started
2019.02.2010:45:28.382 RTS-3.19: load 5264 bytes of history data to synchronize in0:00:00.0072019.02.2010:45:28.382 RTS-3.19: history synchronized from2017.05.04 to 2019.02.192019.02.2010:45:28.383 RTS-3.19: ticks synchronization started
2019.02.2010:45:28.384 RTS-3.19: load 38 bytes of tick data to synchronize in0:00:00.0002019.02.2010:45:28.384 RTS-3.19: history ticks synchronized from2018.12.17 to 2019.02.182019.02.2010:45:28.402 RTS-3.19,M4: history cache allocated for15218 bars and contains 14188 bars from2018.01.0321:16 to 2019.02.1423:482019.02.2010:45:28.402 RTS-3.19,M4: history begins from2018.01.0321:162019.02.2010:45:28.427 RTS-3.19,M4 (Open-Broker): generating based on real ticks
2019.02.2010:45:28.427 RTS-3.19,M4: testing of Indicators\TestCopyTicksRange.ex5 from2019.02.1500:00 to 2019.02.1900:00 started
2019.02.2010:45:28.496 RTS-3.19 : real ticks begin from2018.12.1700:00:002019.02.2010:46:20.8062019.02.1509:45:192019.02.1423:24 - 2019.02.1423:48 ticks_trade=0 ticks_info=0 ticks_all=02019.02.2010:46:20.8092019.02.1509:47:022019.02.1423:24 - 2019.02.1423:48 ticks_trade=0 ticks_info=0 ticks_all=02019.02.2010:46:20.8632019.02.1509:49:472019.02.1423:24 - 2019.02.1423:48 ticks_trade=0 ticks_info=0 ticks_all=02019.02.2010:46:20.9482019.02.1509:55:212019.02.1423:24 - 2019.02.1423:48 ticks_trade=0 ticks_info=0 ticks_all=02019.02.2010:46:21.0322019.02.1509:57:252019.02.1423:24 - 2019.02.1423:48 ticks_trade=0 ticks_info=0 ticks_all=02019.02.2010:46:21.2002019.02.1510:00:002019.02.1423:28 - 2019.02.1510:00 ticks_trade=0 ticks_info=15 ticks_all=152019.02.2010:47:25.0962019.02.1510:04:002019.02.1423:32 - 2019.02.1510:04 ticks_trade=3544 ticks_info=973 ticks_all=45172019.02.2010:47:25.0992019.02.1510:08:002019.02.1423:36 - 2019.02.1510:08 ticks_trade=6246 ticks_info=1469 ticks_all=77152019.02.2010:47:25.1012019.02.1510:12:002019.02.1423:40 - 2019.02.1510:12 ticks_trade=7460 ticks_info=1648 ticks_all=9108
And another question: why was OnCalculate called 5 times before the appearance of ticks (highlighted in yellow in the log)?
Why doesn't the debugging on historical data give the ticks before the test start date? The tester has received them and synchronised them. I understand that in the "All ticks" mode the tester cannot generate ticks before the test start date, but in the "Every tick based on real ticks" mode they are already in the history and synchronized (highlighted in red in the log+)! How then to debug the part of the tick indicator that is based on history data? How to get the ticks of bar time[0] in the OnCalculate in the tester?
And another question: why was OnCalculate called 5 times before the appearance of ticks (highlighted in yellow in the log)?
When testing on a yediotic, they will never give out.
On real ticks, do some testing from a much earlier date so that the ticks are uploaded to the tester agent's database.
OnCalculate is called on every tick. It just gets logged much less frequently, at the start of each subsequent bar to be tested. If, of course, we are talking about my example of indicator
On real ticks, do some testing from a much earlier date to get the ticks uploaded to the tester agent's database.
OnCalculate is called on every tick. It's just that the logging is done much less frequently - at the beginning of each next bar to be tested. If, of course, we are talking about my example of indicator
I posted this compiler bug once before, but no reply, I'll try again:
class A { };
class B : public A { };
class C : public B { };
void f(A &) { }
void f(B &) { } // Должна вызываться эта функция
voidOnStart()
{
C c;
f(c); // 'f' - ambiguous call to overloaded function
}
The compiler generates a false error. There is no ambiguity here. Class B is the closest of the ancestors, so it has priority.
Guys, help me, how do I pass the check before placing the robot on the market. It says it didn't pass validation, but what's the problem, I don't understand. And I don't see tech support on the site
Guys, help me, how do I pass the check before placing the robot on the market. It says it didn't pass validation, but what's the problem, I don't understand. And I don't see tech support on the site
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
No problem. Here's the indicator
Here are the logs
It's true, OnDeinit with control request hasn't been called. Because of the indicator testing. OnDeinit only during debugging
And why during debugging on historical data no ticks are given before test start date? The tester has received them and synchronised them after all. I understand that in the "All ticks" mode the tester cannot generate ticks before the beginning of testing, but in the "Every tick based on real ticks" mode they are present in the history and synchronized (highlighted in red in the log+)! How then to debug the part of the tick indicator that is based on history data? How to get the ticks of bar time[0] in the OnCalculate in the tester?
And another question: why was OnCalculate called 5 times before the appearance of ticks (highlighted in yellow in the log)?
Why doesn't the debugging on historical data give the ticks before the test start date? The tester has received them and synchronised them. I understand that in the "All ticks" mode the tester cannot generate ticks before the test start date, but in the "Every tick based on real ticks" mode they are already in the history and synchronized (highlighted in red in the log+)! How then to debug the part of the tick indicator that is based on history data? How to get the ticks of bar time[0] in the OnCalculate in the tester?
And another question: why was OnCalculate called 5 times before the appearance of ticks (highlighted in yellow in the log)?
When testing on a yediotic, they will never give out.
On real ticks, do some testing from a much earlier date so that the ticks are uploaded to the tester agent's database.
OnCalculate is called on every tick. It just gets logged much less frequently, at the start of each subsequent bar to be tested. If, of course, we are talking about my example of indicator
When testing on the eejit will never give away.
On real ticks, do some testing from a much earlier date to get the ticks uploaded to the tester agent's database.
OnCalculate is called on every tick. It's just that the logging is done much less frequently - at the beginning of each next bar to be tested. If, of course, we are talking about my example of indicator
That's what helped. Thank you so much! :)
Bild 1997. Still not fixed the behaviour of the partial position closing functions. Please correct it before the release.
I posted this compiler bug once before, but no reply, I'll try again:
The compiler generates a false error. There is no ambiguity here. Class B is the closest of the ancestors, so it has priority.
Guys, help me, how do I pass the check before placing the robot on the market. It says it didn't pass validation, but what's the problem, I don't understand. And I don't see tech support on the site
Guys, help me, how do I pass the check before placing the robot on the market. It says it didn't pass validation, but what's the problem, I don't understand. And I don't see tech support on the site
It says in the report what's the problem...
no trading operation
What does it mean?
no trading operation
What does this mean?
How are you going to sell anything on a marketplace with a complete lack of knowledge of English, which is a must for a marketplace?