mrtools wrote: ↑
Wed Jan 06, 2021 4:58 am
friday13 wrote: ↑
Wed Jan 06, 2021 4:05 am
But it is the same, and I am using Chrome, verified the name here in the post is the same as I used it (look at the message also, same file name),
Basically I would love to understand why insert this limitation in the indicator in the first place.
What could be the problem with what I do? By the way, I'm using it inside an EA, not as a resource, but with iCustom.
I forgot to mention the post where I found it, I was sure I quoted it:
That protection is there because sometimes people will download the file and sell it as their own, hopefully this slows that down, might want to check your iCustom call in your EA.
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:
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.