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
Using resources in the tester should work ? It's not working. Error 4802.
Using resources in the tester should work ? It's not working. Error 4802.
What do you really want to do?
Override the calculation function OnCalculate of this indicator in an external indicator with its own calculation engine? You can't do that.
But to check the indicator in the tester you still need the presence of the locking mechanism itself.
Another option is to embed the safety lock completely.
Forum on trading, automated trading systems and testing trading strategies
Discussion of the article "Using Resources in MQL5".
Renat, 2013.01.16 22:21
This was added in the 730 build on 24 November 2012:
Can we make an exception only for TextOut - the ability to work with its own resources of programmes loaded from resources?
Can only for TextOut make an exception - the ability to work with its own resources of programmes loaded from resources?
Where exactly is the problem? What exactly does not work?
There is an indicator, from it the child one is launched, from resources.
TextOut is used in the child one, and the result is loaded to OBJ_BITMAP_LABEL via ResourceCreate, but there is no possibility to use resources in the resource.
The result is that the object appears, the resource is specified in the properties, but the text itself is not output.
There is an indicator, from it a child is launched, from resources.
TextOut is used in the child, and the result is loaded to OBJ_BITMAP_LABEL via ResourceCreate, but there is no possibility to use resources in the resource.
The result is that the object appears, the resource is specified in the properties, but the text itself is not output.
Yes, it is currently impossible to load resources from a resource object.
In fact, the situation looks like this: the indicator "pulled" from a third-party resource starts to live within the called module and all its calls to resources go to the body of the called module, not to the native body. We are currently thinking about this problem and most likely we will solve it.
... We are thinking about this problem now and will probably solve it.