Errors, bugs, questions - page 2625

[Slava]

fxsaber:
Is this a flaw in ArraySwap?

As designed

Exchanges the contents of two dynamic arrays of the same type

[fxsaber]

Slava:

As designed

It turns out that library functions need to somehow tell users that it's better not to send statics.

For example, in some sorting function.

I wonder what's the cheapest way to determine if an array is static?

[Stanislav Korotky]

fxsaber:

I wonder what is the cheapest way to determine if an array is static?

What are the options other thanArrayIsDynamic?

[fxsaber]

Stanislav Korotky:

What are the options other than ArrayIsDynamic?

template <typename T>
bool IsStatic( T &Array[] )
{
  T ArrayTmp[];

  return(!(ArraySwap(Array, ArrayTmp) && ArraySwap(Array, ArrayTmp)));
}

I didn't know about ArrayIsDynamic, thanks.

[Stanislav Korotky]

There's a micro-bug in the article submission interface: it doesn't allow long dashes (-) in the title, even though I'm urged to change single dashes everywhere to long dashes every time.

[Gudgeon]

I wonder if the developers are interested in the bugs posted on the forum?

Maybe I'm not voicing them in the right place?

OK, this bug is#26125- Common inattention to unimportant usability issues.

But this error -#25217 is an obvious bug in memory handling. From version to version.

You don't have ANY INDICATORS WORKING under certain conditions.

And no need to tell the moderators that it is supposedly onVMware x64.

I see this error on 3 machines of mine for more than a year. Everywhere Win 10 x64 only one of them virtual.

PS: If I were you I would pay more attention to stability of your work than to rearrange interface elements from one place to another.

Sorry to be abrupt, but with the second bug, it's getting to the point. I'm working on minutes.

[fxsaber]

Is this the right behaviour?

1. Close the chart.
2. Use File->Open Deleted to restore the chart.
3. The list of deleted charts has not changed. After step 2 I was expecting no restored chart in the list of deleted charts.

[[Deleted]]

fxsaber:

Is this the right behaviour?

1. Close the chart.
2. Use File->Open Deleted to restore the chart.
3. The list of deleted charts has not changed. After step 2 I expected the absence of the restored chart in the list of deleted.

"...... is dead - so dead.

[Slava]

fxsaber:

Is this the right behaviour?

1. Close the chart.
2. Use File->Open Deleted to restore the chart.
3. The list of deleted charts has not changed. After step 2 I was expecting no restored chart in the list of deleted charts.

Yes.

[Stanislav Korotky]

Please explain this behaviour of the tester.

I'm trying to run the Expert Advisor on EURUSD D1 with a full pumped history for a period from the beginning of the year, i.e. 2020.01.01 (I tried 2020.01.02 as the first trading day too), I get 260 bars of history at start!

If I start from 2019.12.31 (the previous bar) - I get 518 bars of history!

Why different values? Why are they so low?

It is clear that we can do different tambourine tricks like special parameters to skip/accumulate some dates/periods, but I would like to clarify the behavior of the tester, not the workaround maneuvers.