Errors, bugs, questions - page 1397
![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
And secondly, we need to use this indicator buffer value in other indicators and Expert Advisors,
and something tells me that if you make a buffer for calculations, it will be impossible to get its value through iCustom.
By the way, I don't remember exactly, but I think you can. Give it a try. )
Even so, I have a dozen indicators with attributes like DRAW_NONE calling one another, and then I already need some separate subsystem that groups in one place readings from all working indicators by mouse pointer position. :)
Compilation error:'a' - is not static member
but that's OK. What's the difference?
I don't know about you, but I already see several compiler errors.
1) it doesn't distinguish between functions and variables when inheriting.
2) the variable of the base class is private, so first the message that it is impossible to access the private members should come out
I don't know about you, but I already see several compiler errors.
1) it doesn't distinguish between functions and variables when inheriting.
2) the variable of the base class is private, so first the message that it is impossible to access the private members should come out
Give me some examples. It is interesting to see in which cases such problems in terms of code design.
I think I've already given examples. But I will make it more detailed to make it even clearer:
Note that in the third example in class A I replaced the variable name with "h" and this code compiles (of course if you comment out 1 and 2 examples), which confirms my hunch.
Situation: the test is on H1 (I think it is important - we are talking about a multi-period test). The last daily (D1) bar in the tester SeriesInfoInteger gives for example 2015.10.08. I take the iMA indicator on D1 with an offset of 2. It gives the value for 2015.10.05 (which should be 2015.10.06 with an offset of 2).
It means that the indicator lags in the tester compared to time series creation. It happens clearly at the start of a new D1 bar. Has anyone experienced such a situation? I will not simulate the example yet.
Situation: The test is on H1. The last daily (D1) bar in the tester SeriesInfoInteger gives for example 2015.10.08. I take iMA indicator readings with an offset of 2. It gives the value for 2015.10.05 (which should be 2015.10.06 with an offset of 2).
That is, the indicator lags in the tester compared to the construction of the timeseries. Has anyone had this happen? I am not going to simulate an example yet.