
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
Subject:
So?
Start the indicator, then - the Expert Advisor
You notice that the indicator buffer values (CTRL+D) do not coincide with iCustom values (they are printed in the Expert Advisor's chart comment).
In case of our test, iCustom will give either EMPTY_VALUE or zero.
Checked. It's not that it doesn't match, it's not there at all. Pretty cool.
For some reason they still can't do a human readout of the indicator data from the chart! It sounds crazy, but it is.
The problem is in the problem statement.
You're just using the indicators for the wrong purpose. They're not designed to be timed and react to events, they're designed to economically rework time-series.
Approach your task from the other side and you will find a nice and economical solution.
It's not about reading buffers, it's about the fact that the indicator called via iCustom() has no timer and no chart events.
What are they for?
Well, seriously, what for?
What are they for?
Well, seriously, why?
The problem is in the problem statement.
You are simply using the indicators for the wrong purpose. They are not designed to be timed and react to events, they are designed to economically rework time-series.
Approach your task from the other side and you will find a nice and economical solution.
It's like a hammer on the head to make such a statement. I decided to look for indicators in kodobase. I haven't found ANY that uses the usual approach: event-driven model + OOP.
It's hard to say what's more: frustration or disappointment with this state of affairs. Indicators, it turns out, MUST be written primitively.
Does anyone use the event model + OOP in indicators?
Well it still doesn't negate the perplexity that you can't programmatically get what you see with your eyes on a chart!
It's like a kick in the head to make a statement like that. I decided to look for indicators in kodobase. I haven't found ANY that uses what I'm used to: event-driven model + OOP.
It's hard to say what's more: frustration or disappointment with this state of affairs. Indicators, it turns out, MUST be written primitively.
Does anyone use the event model + OOP in indicators?
Well it still doesn't negate the perplexity that you can't programmatically get what you see with your eyes on a chart!