New MetaTrader 4 Client Terminal Build 507: Trading Signal Registration Command and Setting a Spread When Testing - page 6
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
I've reported it to the Service Desk with code and a link to this thread.
Thank you.
I've reported it to the Service Desk with code and a link to this thread.
Awesome!
I don't have enough information and cannot provide code to reproduce the issue.
Just put an unused function at the top of your code. That'll do it.
Just put an unused function at the top of your code. That'll do it.
I had a very peculiar issue this morning after my MT4 platform had updated to build 507. An EA that I had been happily compiling and running on Friday suddenly started failing to load with the message: "executable file is corrupted. Please recompile it." Just to be sure that everything was the same build level, I downloaded and reinstalled MT4, which had no effect on the problem.
After some investigation, I think I have tracked the problem to having some internet access code in a function that is not actually called by the EA. For example, the code shown below, when compiled, gives me the "corrupted" message when I drag it onto a chart. If, however, I open up the commented lines, recompile and run it, the call appears to work ok and prints a reasonable value for stringlen(sData).
I have other EAs that use this code to access internet data and they all appear to be working ok after recompilation. It just seems to be the fact of having the code in the EA but not calling it that causes the issue.
Anyone any ideas what might be wrong?
Thanks, Greg
I had a very peculiar issue this morning after my MT4 platform had updated to build 507. An EA that I had been happily compiling and running on Friday suddenly started failing to load with the message: "executable file is corrupted. Please recompile it." Just to be sure that everything was the same build level, I downloaded and reinstalled MT4, which had no effect on the problem.
After some investigation, I think I have tracked the problem to having some internet access code in a function that is not actually called by the EA. For example, the code shown below, when compiled, gives me the "corrupted" message when I drag it onto a chart. If, however, I open up the commented lines, recompile and run it, the call appears to work ok and prints a reasonable value for stringlen(sData).
I have other EAs that use this code to access internet data and they all appear to be working ok after recompilation. It just seems to be the fact of having the code in the EA but not calling it that causes the issue.
Anyone any ideas what might be wrong?
OK, thanks for posting code, I can reproduce this issue when using your code as a script . . .
2013.06.24 10:29:54 gregspinner GBPUSD,H1: executable file is corrupted. Please recompile it.
I suspect that it is related to the imports and not just simply having code that is unused . . .
Having the same problem.. buid 507. To me it seems like the problem has something to do with dll. After moving indicator that 507 claimed to be corrupted to another terminal i was able to run it but it did not start executable which was supposed to be started by ShellExecuteA from within the indicator, neither did dll api to that executable work after manually starting the exe.
I did try to locate the problem by quoting of some code but as a result of recompiling terminal crashed and wont start again...
I won't post my confidential code either.
I've Windows 7 x64, UAC turned off and I'm outside the Program Files (x86) directory.
If I'm using my own include files, I got the "executable file is corrupted. Please recompile it." error message. If I copy'n'paste the code from the mqh files, the error message is gone.
I agree with RaptorUK, the problem is not with the unused code but the import mqh files.
My include file structure working flawless since build 226, so I guess I could go out to have a coffee instead of worry about my working code turning in to something unusable by one upgrade.
I'm always using build 226 compiler, so I'm not frightened.
Bugs are bugs, I can see that. The problem is MetaQuotes publishing their new builds too early, forcing many people into changes which were demanded years ago. Nobody will die if the testing period will expand the release date of any kind of new build.
By the way, regarding the new version's description (first post of this topic):
1) the distance calculation shouldn't be writing pips; it should be points. 1 classic pip equals 10 points in 3/5 digits forex symbols.
2) the first image is fake and wrong. 55 points (not pips!) is the distance between the new sell limit and the current bid price, and not between the old and new desired sell limit.
3) Of course, with usual broker condition 55 pips of 1.00 lot EURUSD generates 550 USD profit or loss, so this points to my first observation - points, not pips!