Welcome to Forex-TSD!, one of the largest Forex forums worldwide, where you will be able to find the most complete and reliable Forex information imaginable.
From the list below, select the forum that you want to visit and register to post, as many times you want. It’s absolutely free. Click here for registering on Forex-TSD.
Exclusive Forum
The Exclusive Forum is the only paid section. Once you subscribe, you will get free access to real cutting-edge Trading Systems (automated and not), Indicators, Signals, Articles, etc., that will help and guide you, in ways that you could only imagine, with your Forex trading.
Elite Section
Get access to private discussions, specialized support, indicators and trading systems reported every week.
Advanced Elite Section
For professional traders, trading system developers and any other member who may need to use and/or convert, the most cutting-edge exclusive indicators and trading systems for MT4 and MT5.
it seems that mt4 vuild 213 has problem with string handling, it crashes most of my indicators and EA. Here are some simple fix:
1) avoid passing string lateral in function parameter instead pass by variable type string.
BAD: Print("This is a test");
OK: string strTemp = "This is a test";
Print(strTemp);
2) avoid using operator + to concatenate string, use buildin function StringConcatenate():
BAD: int i=0;
Print("This is index i="+i);
OK: int i=0;
string strTemp = StringConcatenate("This is index i=",i);
Print(strTemp);
it solves my problems, I hope it helps u too..
Print();
Hi. I have EA's running on build 213 that are coded in the manner you suggest, and can't say I have seen any of the problems you describe. btw, when using really long strings (ie. buffering web-pages etc.) StringConcatenate() does not allocate memory properly - search Metaquotes forum if you need more info.
If you are having crash problems with b213: MetaQuotes has an updated version of b213 up. It is dated March 25th. Read down about 10 posts in this thread. It solved problems I had with platform crashes. I did re-compile EAs and indicators.
What’s new:
1. MQL4: Fixed error of constant string concatenation (Expert Advisors and scripts compiled in build 213 must be recompiled).
2. MQL4: Fixed error of the reinitialization of global and static variables of MQL4-libraries.
3. MQL4: Fixed memory leak when resizing of string arrays.
4. MQL4: Fixed memory leak when accessing out of range of string arrays.
5. Tester: Fixed error of generating ticks in candlesticks with volume 4–6 and with one shadow absent.
What exactly is the problem? I have the 'old' version (13th March) and have experienced no crashes...
I crashed 4 of my demo platforms on NF with 213. Now I have issues with FXPro.com's demo platforms - None of my EA's will work with the platform even since 215 came out tonight - I keep getting error 130 and I don't get this on other brokerage demo accounts.
I crashed 4 of my demo platforms on NF with 213. Now I have issues with FXPro.com's demo platforms - None of my EA's will work with the platform even since 215 came out tonight - I keep getting error 130 and I don't get this on other brokerage demo accounts.
I crashed 4 of my demo platforms on NF with 213. Now I have issues with FXPro.com's demo platforms - None of my EA's will work with the platform even since 215 came out tonight - I keep getting error 130 and I don't get this on other brokerage demo accounts.
Dave
There is obviously something wrong with MT with all these complaints, but with build 213 March 13, I get no problems! As I leave things running 24/7 I don't get prompted about new updates (normally, when MT crashes) but having just checked, I see I'm two updates behind...
Think I'll leave well enough alone till they sort things out...
Linear Mode
