Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
ad 1.)
Pardon, but the first sentence doesn't make sense.
Indicators are supposed to be called by strategies.
So - if called correctly - why should a call deliver less than the indicator can do?
ad 2.)
From a performance point of view:
Why would one pack x time series into a strategy that uses indicators that hold these time series anyway?
Can you help answer these questions from other members on NexusFi?
What I meant is that when I try to use my indicator from within a strategy (via AddChartIndicator), the strategy fails to run because the indicator is referencing BarsPeriod. However, this does not cause problems when the indicator is just added to a chart (for visual purposes only).
Ok, so the problem was more basic
AddChartIndicator is nothing but a visual representation without any flexibility concerning calculations.
But that is also made clear in the manual ...
I've played around with it a bit more. It seems a workaround for this problem would be to not define my indicator in State.Configure, but instead wait till OnBarUpdate to do so (of course with logic implemented so this code snippet is only called once). It's working fine now, tested with all three lines of AddDataSeries.
I guess the only drawback is that since it's not defined in State.Configure, I can't AddChartIndicator, so I don't have the visual representation but I can live with that. It would be nice to have though, and am surprised this took a step back since it worked fine in NT7.