One additional thought about that strategy/indicator discussion...
It will be a good habit to break up different indicators and strategies into separate parts.
Want to know why?
Part of my plan to make TickZOOM faster will be to make more of your logic run in "parallel".
Let's say you have strategy A which includes indicators B, C, and D.
Well TickZOOM will automatically work out those dependencies and it can calculate the B, C, and D formulas at the same time on different CPUs.
Once those results are done, then it can calculate your strategy A.
If you, instead, glum all that code into strategy A without B,C,andD. you lose out on that performance gain.
Now that is future.
But won't that be cool? Just to separate out the code and WHAM it runs much faster?
Wayne
It will be a good habit to break up different indicators and strategies into separate parts.
Want to know why?
Part of my plan to make TickZOOM faster will be to make more of your logic run in "parallel".
Let's say you have strategy A which includes indicators B, C, and D.
Well TickZOOM will automatically work out those dependencies and it can calculate the B, C, and D formulas at the same time on different CPUs.
Once those results are done, then it can calculate your strategy A.
If you, instead, glum all that code into strategy A without B,C,andD. you lose out on that performance gain.
Now that is future.
But won't that be cool? Just to separate out the code and WHAM it runs much faster?
Wayne

