Apologize didn't realize you had that much coding experience.friday13 wrote: Fri Jan 08, 2021 12:07 pm
H again,
What do you mean "might want to check the iCustom call"? It is quite a vague suggestion to me.
If it doesn't return an error, then it reads the indicator correctly, but for some reason the indicator returns these messages printed in the log file.
I'm a programmer for 12 years, I know MQL4 very well, but if this indicator perhaps calls on itself while running, then maybe the coding of it is incorrect, so it cannot be used in an EA.
If it only checks for its name, then the method to check the name should be changed, if you use WindowExpertName() it is not good, you should be reading it as suggested in the last part of this link:
https://docs.mql4.com/runtime/resources
Isn't there anyone who experienced the same issue I have? I sent my EA to another person, with the link to this website, and he received the same result, the buffers cannot be read in the EA, and these messages are printed over and over again.
Please help me figure it out, if you used it in an EA, then share how you used it, this is the first time I encounter such an issue and this name protection type.
This is using a newer renaming protection hopefully it will work better in your EA after that not sure what else to do, not sure how you are calling it but if your using the trend buffer it is buffer #4.
