Upcoming Empty4 4 and MQL4 Upgrades

[dietcoke]

I've come across this which is relevant to anyone who uses OUtputDebugStringA to get the kernal debugging.

It doesn't work any more in 600

You have to use the W (Unicode) version of the function as below

Code: Select all

#import 		"kernel32.dll"
	void		OutputDebugStringW(string msg);
#import

[AnotherBrian]

This is cool, for you coders.

Code Profile

[PIPone]

ahah , Build 600 the darkness of evil.....

" One Market to rule them all, One Market to find them,

One Market to bring them all and in the darkness bind them,

In the Land of Meta Quotes where the Shadows lie. "


The Lord of MetaQuotes

[jlcgarcia]

ahah , Build 600 the darkness of evil.....

" One Market to rule them all, One Market to find them,

One Market to bring them all and in the darkness bind them,

In the Land of Meta Quotes where the Shadows lie. "


The Lord of MetaQuotes

Hi friends,


With the new Empty4 600 many things have changed. At present main areas of change seem to be:

-New reserved words may clash with old variable names (char, new etc )
-Data Paths
-unicode strings (sending /receiving string to DLLs - use unicode version of library calls OR convert strings to char array)
-datetime is 64bit
-ArrayResize return result is different
-Arrays are always pass by value.
-FileWriteArray doesnt work with strings
-Replace ArrayCopyRates with CopyRates.
-StringSubstr is changed.


As I cannot cope with so many changes in the code, the best solution (I think) for the new Empty4 600 is the following (that I am using) :


By clicking the link below you can find the attached archive with build 509 of MQ4. The Metaeditor executable file is itself enclosed.
1. Unzip the archive into the folder you like.
2. Find Metaeditor.exe and run it by double clicking.
3. Go to menu File -> Open (as soon as Metaeditor starts working).
4. Find the MQ4 (of EAs or indicators ) file you want to compile in order to use it in the new build 600. Click the Compile button to compile the MQ4 file.
5. Find the EX4 executable file in the same folder, where the MQ4 file is placed at.
6. Copy this EX4 file in to the MQ4 /experts or indicators folder of build 600. Run the new build.

Regards


José Luis

MetasEditor_509.zip

[dietcoke]

coders, the arseholes have broken

Code: Select all

StringSubstr

http://www.forexfactory.com/showthread. ... ost7268143

[Pedigree]

Hi friends,
With the new Empty4 600 many things have changed....
As I cannot cope with so many changes in the code, the best solution (I think) for the new Empty4 600 is the following (that I am using) :

By clicking the link below you can find the attached archive with build 509 of MQ4. The Metaeditor executable file is itself enclosed.
1. Unzip the archive into the folder you like.
2. Find Metaeditor.exe and run it by double clicking.
3. Go to menu File -> Open (as soon as Metaeditor starts working).
4. Find the MQ4 (of EAs or indicators ) file you want to compile in order to use it in the new build 600. Click the Compile button to compile the MQ4 file.
5. Find the EX4 executable file in the same folder, where the MQ4 file is placed at.
6. Copy this EX4 file in to the MQ4 /experts or indicators folder of build 600. Run the new build.

Regards
José Luis

Really, how long can an old build run for? Is it not dependent on the continued support of the broker, or can it simply be kept indefinitely alive by not upgrading?

And is anyone out there still able to use any builds much older than 509? That would be surprising because there was really no cause to do that. But now, probably more than ever before, there is REAL cause to want to do it.

Meanwhile, the devastation continues: some files that worked in build 600 are no longer working in 602! There's no telling what will stop working one week down the line.

[PIPone]

Very bad news friends,

I backtested the same .exe file (compiled with buil 509) both with the strategy tester of build 509 and with the strategy tester of build 604.
Imagine what? The result of trading during BT with B604 is completely flawed.

Be very cautious with all EAs compiled with B509, I strongly recommend to back test all EAs under the new Build >600, before run them on real.

Good luck !

[gms]

Is it it just me or did anyone else notice that running multiple instances of 604 terminals uses much more CPU resources than older builds? With 509 I could run 6 instances without a problem. Now my computer has problems with 3. And it is even worse on my VPS ...

Gary

[nonlinear]

I loaded one instance of the new build on my VPS to test it out and it nearly crashed. I used to be able to run more Empty4 instances. Not any more. This really sucks. I do not need the facebook of trading software. I want reliability and speed with features that matter. Ok, I am going to go puke now. Thanks MQ.

[brinol]

This from C2Algo the Mlq to C# converter software company servicing CAlgo.....thought I might share their response to my question the other night .Anything is better than nothing right ?


Message: Hi guys . I have a few Ea's that i would like converted to c# . I have tried your converter but with no joy..Do you provide an added conversion service and if so what would the cost be?
Best Regards : Brian


Dear Brian

We are preparing a fancy update for 2calgo.com. In couple of weeks the conversion rate will be increased. Please try to convert your EA later.

2calgo team.