Errors, bugs, questions - page 1044

 
Left a comment in the marketplace, will there be a reply notice ?
 
Found it)

SYMBOL_SESSION_PRICE_SETTLEMENT

Supply price for the current session

Question why all variables in help do not correspond to their names in the terminal)

 
Could you please tell me if an EA designed for 4-digit quotes can work on 5-digit quotes?
 
yosuf:
Could you please tell me if an EA designed for 4-digit quotes can work on 5-digits?
It can rather than not.
 
yosuf:
Please tell me if an EA developed for 4-digit quotes can work on 5-digit ones?

Yes it will work (most likely), just zeros will be assigned to the fifth digit, but the opposite is more difficult, if there is no special gearing it may fail due to the roughness of the calculation.

But we should check the logic and see if there are constants instead of calculations, and then the first option might not work, depending on the diligence of the programmer.

 
yosuf:
Could you please tell me if an EA developed for 4 digits can work on 5 digits?
For example, when I send an order for a 4-digit quote, there may be a slippage of 3 pips and if it stays like that, it will be 0.3 pips for a 5-digit quote. Then for a 5-digit order we should set 30 pips, we should look for such things in the code.
 
yosuf:
Could you please tell me if an EA developed for 4-digit quotes can work on 5-digits?

Have a look at the five-mark examples of the MACD Sample Expert Advisor

The Expert Advisor was developed a long time ago and is designed for 2 or 4 signs. In 5, it was tuned for 3 or 5 digits. The m_adjusted_point variable is responsible for this

 
stringo:

Slava, what are the new trends with zeroing in calculators prev_calculated on every tick ?

How long will it last?

The processing scheme of prev_calculated / rates_total was supposed to be economical.

And what do we have now? :

2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:07     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:06     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:06     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:06     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:05     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:05     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:05     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:05     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:04     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:04     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:04     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:03     MaxEqZZ (EURUSD.m,M1)   prev_calculated ==0
2013.08.20 13:04:03     MaxEqZZ (EURUSD.m,M1)   prev_calculated ==100001
2013.08.20 13:04:03     MaxEqZZ (EURUSD.m,M1)   prev_calculated ==100000
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==0
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000
2013.08.20 13:04:03     MaxEqZZ (CHFJPY.m,M1)   prev_calculated ==100000

Two or three calls of OnCalculate(...) at every tick and the last one requires recalculating indicator completely from zero.

My room is already "tachkent" - video card is overheating (calculating a bunch of heavy indicators in OpenCL).

--

How to live?

Документация по MQL5: Основы языка / Функции / Функции обработки событий
Документация по MQL5: Основы языка / Функции / Функции обработки событий
  • www.mql5.com
Основы языка / Функции / Функции обработки событий - Документация по MQL5
 
MetaDriver:

Slava, what are the new trends with zeroing in calculators prev_calculated on every tick ?

How long will it last?

The processing scheme of prev_calculated / rates_total was supposed to be economical.

And what do we have now? :

Two or three calls OnCalculate(...) on every tick, the last one requiring full recalculation of indicator from scratch.

My room is already "tachkent" - video card is overheating (calculating a bunch of heavy indicators on OpenCL).

--

How to live? NadaCalculate!

About a month ago this issue already came up. We have not been able to reproduce this problem in our

Don't you have calls of this indicator from the Expert Advisor?

 
stringo:

This issue already came up about a month ago.

1) We have not been able to reproduce this problem with ourselves

2) Do you have any calls of this indicator from Expert Advisor?

2) There are no calls from the expert

1) I will help :)

In the trailer you can enable/disable calling of CopyRates() and writing of values in buffer.

In "empty" variant (as you probably checked) it works according to specification (prev_calculated on each tick is not zeroed and called once).

But "under load" (when copying/writing values) it starts messing around.


Check it:

Документация по MQL5: Доступ к таймсериям и индикаторам / CopyRates
Документация по MQL5: Доступ к таймсериям и индикаторам / CopyRates
  • www.mql5.com
Доступ к таймсериям и индикаторам / CopyRates - Документация по MQL5
Files: