Open OpenTrading opened 10 years ago
If you could add a file or a section of the documentation as to which MT4 builds of MT4 each branch of mql4zmq is known to work with, along with OS version and environment (e.g. Wine), it would help people know if it "should" work out of the box.
Careful: MetaQuotes may have rolled out an end-to-end string to Unicode conversion with a buggy StringToCharArray function! See: http://forum.mql4.com/60694/page5 Maybe this has been fixed, but it will need testing.
This is due to changes that rolled out with MT4 build 610. The v.2 beta patch should have fixed this issue. I have been working on v.2 RC which will address the changes in a simpler fashion. It's currently still in testing, but I'm optimistic that I'll be able to push it to the public repo next week.
Regarding ZMQ, internally we have V3 under development which will move to ZMQ v4.
Great news - I look forward to the RC. Where can I find the "v.2 beta patch "?
Any progress on this? The current branch does not work for me on Build 625. The Experts log says a tick is published, but the python tickcollector does not see anything....
We've forked this and have it working with >=Build 600 and ZeroMQ 2.2.0 at https://github.com/OpenTrading/mql4zmq
MetaQuotes has done it again: http://mechanicalforex.com/2014/02/dealing-with-the-latest-mt4-build-600.html
They rolled out an automatic upgrade to MetaTrader 4 that broke every EA or Indicator in the world that passes any string to a DLL! They made an end-to-end substitution of Unicode UTF-16 for char strings.
The need for a communications mechanism and bridge under Mt4 is now extreme. Could you update the mql4zmq code on github to deal with this? It shouldn't be much work, as it's just the few strings, but I don't know C.
Perhaps if you could open a 3.x branch on github and maybe if you have time, update the zmq to 3.x, which also is only a small amount of changes.
I can help you with the bridge, and with testing.