1. tester passes first 100 bars without processing
2. use normal shift and don't mention it.
3. global variables are useful when several experts are interprocessed. if some custom indicator sets global variable then expert advisor need to call such indicator to get correct global variable. and this indicator must be removed from all the charts to avoid interference
2. use normal shift and don't mention it.
3. global variables are useful when several experts are interprocessed. if some custom indicator sets global variable then expert advisor need to call such indicator to get correct global variable. and this indicator must be removed from all the charts to avoid interference
![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
when backtesting you must have the correct "shift" for iCustom function. What approach has been given to get a value from the custom indicator into EA when backtesting. I have tried with counting and transferring bars from the indicator to EA through global variable, but no luck 'till now, because of the backtester behaviour mentioned above. Am I missing something here?
I am shure you guys have had this in your mind when writing backtester?
Regards, Mike