Can you be more specific about why it's bad? Why do we need a new type a long time ago?
Seems like a perfectly acceptable solution to me. We must take all time in milliseconds, time*1000+msc - here is the same long (or what is ulong now?). And output via ArrayPrint() will be understandable.
Speed just not the maximum, so that the test takes some time, in the process of which hangs. True, not always - I do not understand what it depends on, whether it's mouse movements or something else. In general, you can test it several times, it should hang.
Here we have a classic deadlock of two synchronizers. Just like in Richter's book.
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.
Better just make it an msc field and write milliseconds (0-999) to it separately.
This is the worst solution.
The datetime_msc type has been needed for a long time.
This is the worst solution.
The datetime_msc type is long overdue.
Can you be more specific about why it's bad? Why do we need a new type a long time ago?
Seems like a perfectly acceptable solution to me. We must take all time in milliseconds, time*1000+msc - here is the same long (or what is ulong now?). And output via ArrayPrint() will be understandable.
Generally speaking, as far as the tester hangs up. I have been able to identify several functions that cause it. The most common is Comment.
Here try to run such an indicator in the tester:
int OnCalculate(const int rates_total, const int prev_calculated, const int begin, const double &price[])
{
Comment("OnCalculate");
return rates_total;
}
Speed just not the maximum, so that the test takes some time, in the process of which hangs. True, not always - I do not understand what it depends on, whether it's mouse movements or something else. In general, you can test it several times, it should hang.
Here we have a classic deadlock of two synchronizers. Just like in Richter's book.
Fixed it. Thanks. (chuckles)