Any rookie question, so as not to clutter up the forum. Professionals, don't pass by. Nowhere without you - 6. - page 735

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
Please tell me how to do it.
or embed in the EA code, or run the indicator in parallel with the EA to read the position of the desired object in the chart from the EA.
Or add a buffer(s) to the indicator code and output the data of graphic objects in it(them).
SZZ did not look at sources. I just made my suggestion, because I myself have already had to insert the necessary buffers in the bufferless indicator, instead of reading the data of graphical objects.
The second way is clearly a dead end. I can't do the first one, so I guess I need to do something more appropriate to my level)
Or add a buffer(s) to the indicator code and output graphical object data to it.
I didn't look at the source code. I just made my suggestion, because I already had to insert the necessary buffers into the bufferless indicator myself, not to read the data of graphical objects.
I had to write indicator_separate_window with buffers and chart. So, when iCustom() called the indicator from the EA, the trend lines were drawn on the chart, even if there was no indicator on the chart. I even had to set NONE for colour when calling from the EA. However it was before global changes of MT builds. I have to check how it will work now.
The indicator runs and does what it should do.
It's just not convenient to take the data from graphical objects into the EA - there will be no data in the tester, only in visualization mode, which is not convenient. The optimisation in general has gone up in smoke then.
The second way is obviously a dead end. I can't handle the first one, so I guess I need to do something more appropriate to my level)
Well, yes, everything is correct - the indicator runs and does what it is supposed to do.
It's just not convenient to take data from graphical objects into the EA - they won't be in the tester, only in visualization mode, which is not convenient. The optimisation in general has gone to smoke at that time.