Disliked{quote} Source code for VOConsole is written in Clarion, for which the compiler costs USD 2,000. Anybody wanting to maintain VOConsole would first need to buy the compiler from its manufacturer, Soft Velocity. Presumably this would deter folk from pursuing anything on a non-commercial basis, but I'm open to discussion, if anybody's interested.Ignored
VO-Pro: Comprehensive visual order management system for MT4
- #885
- Edited 5:52pm Jan 31, 2014 11:55am | Edited 5:52pm
- Joined Sep 2006 | Status: ... | 8,113 Posts
Just to clarify the current position:
The e-mail that I sent was written after I’d read post #878:
along with info in these threads (here and here). All of this seemed to suggest that VO-Pro would not work correctly on future MT4 builds. I thought it best to give everybody some advance warning.
I haven’t tried build 574 yet myself. I no longer use VO myself; what little forex trading I do nowadays is accomplished using a handful of other EAs that execute a semi-automated strategy. Forex is only a tiny part of my overall investment strategy, and if the new look MT4 is going to make things unduly difficult, I’ll quit forex altogether.
When my br0ker (Pepperstone) releases build 574 (or whatever the latest build number is), I’ll attempt to run VO on it, and report my findings.
Some technical info, in case it’s helpful:
MetaQuotes claim here that existing .ex4 files (EAs/indicators/scripts) can be ported ‘as is’ into the new look MT4, and will run correctly. If this is true, then difficulties arise only if programmers need to modify them. In which case programmers have two choices:
#1. Maintain two separate versions of MT4. Make the changes using the ‘old’ MQL4 programming language (build 509). Then exit MT4 (build 574), copy the .ex4 from build 509 to 574, and restart MT4 (build 574), so that it will pick up the newly modified .ex4 file. A unduly clumsy and time-consuming process.
Testing code on build 509 will remain possible until MetaQuotes compel brokers to discontinue the price feed on that build. After that, all testing would need to be performed on build 574, which means going through the cumbersome process of copying the .ex4 file, and exiting and restarting MT4 (which takes 3–4 minutes on my computer) every time the programmer needs to test even the tiniest change.
#2. The alternative is to commit entirely to the new look MT4 (build 574). This effectively means learning an ‘object oriented’ programming language and rewriting all EAs/indicators/scripts, and then maintaining them, using build 574's editor and compiler.
Given my income from forex, I can’t justify #2. More than 700 hours development went into VO, and having to shelve my existing projects to learn a new language and completely rewrite the four VO scripts and ‘VO monitor’ EA is simply not a viable option for me. (Note: I will likewise not be upgrading any of the free indicators that I've shared on the Platform Tech forum).
Hence the upshot of all this is:
--- In so much as the VO scripts and EA continue to run ‘as is’ on future MT4 builds, VO will remain useable.
--- If/when this is no longer the case, the only way to run VO would be to maintain a copy of build 509 (assuming you can find a br0ker that still maintains a price feed).
--- When this is no longer possible, it is the end of the road for VO.
David
The e-mail that I sent was written after I’d read post #878:
Just downloaded the beta 579 to test and VO pro doesn't work. The folder structure is different on this new build and even when you try and move the scripts etc they don't execute on the charts. Loads of indicators not working either. Way to go Metatrader.
I haven’t tried build 574 yet myself. I no longer use VO myself; what little forex trading I do nowadays is accomplished using a handful of other EAs that execute a semi-automated strategy. Forex is only a tiny part of my overall investment strategy, and if the new look MT4 is going to make things unduly difficult, I’ll quit forex altogether.
When my br0ker (Pepperstone) releases build 574 (or whatever the latest build number is), I’ll attempt to run VO on it, and report my findings.
Some technical info, in case it’s helpful:
MetaQuotes claim here that existing .ex4 files (EAs/indicators/scripts) can be ported ‘as is’ into the new look MT4, and will run correctly. If this is true, then difficulties arise only if programmers need to modify them. In which case programmers have two choices:
#1. Maintain two separate versions of MT4. Make the changes using the ‘old’ MQL4 programming language (build 509). Then exit MT4 (build 574), copy the .ex4 from build 509 to 574, and restart MT4 (build 574), so that it will pick up the newly modified .ex4 file. A unduly clumsy and time-consuming process.
Testing code on build 509 will remain possible until MetaQuotes compel brokers to discontinue the price feed on that build. After that, all testing would need to be performed on build 574, which means going through the cumbersome process of copying the .ex4 file, and exiting and restarting MT4 (which takes 3–4 minutes on my computer) every time the programmer needs to test even the tiniest change.
#2. The alternative is to commit entirely to the new look MT4 (build 574). This effectively means learning an ‘object oriented’ programming language and rewriting all EAs/indicators/scripts, and then maintaining them, using build 574's editor and compiler.
Given my income from forex, I can’t justify #2. More than 700 hours development went into VO, and having to shelve my existing projects to learn a new language and completely rewrite the four VO scripts and ‘VO monitor’ EA is simply not a viable option for me. (Note: I will likewise not be upgrading any of the free indicators that I've shared on the Platform Tech forum).
Hence the upshot of all this is:
--- In so much as the VO scripts and EA continue to run ‘as is’ on future MT4 builds, VO will remain useable.
--- If/when this is no longer the case, the only way to run VO would be to maintain a copy of build 509 (assuming you can find a br0ker that still maintains a price feed).
--- When this is no longer possible, it is the end of the road for VO.
David
- #887
- Feb 4, 2014 6:50pm Feb 4, 2014 6:50pm
After mysteriously getting updated to 574 about two weeks ago and finding my VOPro busted...I was able to go back to build 509. I guess my bitcoin trading version of mt4 from BTC-e was upgraded so it upgraded all my mt4 platforms.
Now however, my broker has rolled out build 600, which of course broke everything again. Strange thing is this time there is no MQL4 folder in my mt4 directory structure...so I have no idea how to try and fix my indis and scripts. Anyone else hear anything like this? I will check those other threads and see if I can figure something out. I won't give up my VOPro without a fight!!!
Now however, my broker has rolled out build 600, which of course broke everything again. Strange thing is this time there is no MQL4 folder in my mt4 directory structure...so I have no idea how to try and fix my indis and scripts. Anyone else hear anything like this? I will check those other threads and see if I can figure something out. I won't give up my VOPro without a fight!!!
- #888
- Edited Feb 5, 2014 12:24am Feb 4, 2014 10:09pm | Edited Feb 5, 2014 12:24am
- Joined Sep 2006 | Status: ... | 8,113 Posts
