MetaEditor build 1463 - page 16

[fxsaber]

Alexey Kozitsyn:
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.

[[Deleted]]

fxsaber:

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.

[Slava]

Alexey Navoykov:

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:

#property indicator_separate_window

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)