Thanks Bruce for bringing this up and Rene for confirming it.renexxxx » Thu Nov 09, 2017 12:24 am wrote:Yes, that is true. An EA will load and cache in memory an instance of the indicator for each unique combination of its input parameters, as specified in the iCustom call. This can be demonstrated by the attached TestEA and TestIndicator: In the OnInit of TestIndicator there is a print statement telling us that it is being initialized. The TestEA loads TestIndicator with three different sets of input parameters: therefore Empty4 loads three different instances of the indicator and keeps them cached in memory -- resulting in only three print statements.Bruster400 » Thu Nov 09, 2017 7:22 am wrote: On a separate note, I read somewhere that iCustom had been improved in one of the recent build changes and it is now much faster. I can't find the post () but the general gist was that the calls have been improved by only initialising the indicator once and keeping it open in memory with all the buffers populated so that it doesn't recalculate historic bars on each new call. Of course that's all great if it actually works!....
It will not stop me being rude about Crap Custom Abortions (not an epithet applied to the excellent indicators coded by the fantastic coders here), but it does mean I do not have to worry about cpu's emitting blue smoke any more.
)