My Swissquote MT4 accountaswas updated. I understood that all the new files hierarchy was set up, but the program continued to refer to the old file-locations. So I trashed all MT4 instances and installed from scratch. Still Swissquote MT4 build 610 does not open profiles in the new locations but reinstalls them in the old locations and looks for the there.
Can I tell MT4 the path, where to look for indicators, ea, templates, profiles etc?
Is this a Swissquote MT4 problem or did you encoiunter this with other provider's updates?
Thanks for your help Mike
SaveAs an indicator - you should then see the path
MS did for a long time with XP etc etc
Point remains that Build 600 has 'broken' a lot of EAs etc, so supporting two MT4 builds would possibly be the least of two evils, at least for a year or so.
Vista - now that would be sad.
It would have made more sense to 'freeze' MT4 build 509 32 bit for legacy OS and providing the option of MT4 build 600+ for those desiiring to run MT4 64bit. At least users would then feel that they had a choice.
A friend of mine pointed me to an article:
<link removed by moderator>
Here's my reply:
That's GREAT news Jay! What this means is that MetaQuotes are changing things, and although they have forced an upgrade by the way they have handled it, for the informed and those that code MQL4, we can continue to use the old AND the new, so that us developers have TIME to sort through this crap that been thrown our way without our permission first (breaking many of the advanced coders previously working compiled code in the process).
I appreciate SDC and angevoyageur inputs. I agree with angevoyageur method:
"angevoyageur said to me a while back, code in the old mql4 style unless you need the new functionality. I think that is good advice. There are only a few small changes to learn about if you take it that way."
Is there a manual that can walk us through and show us what changes, including examples? This would really help us developers. Then a separate manual showing the indeed new stuff. Because we not only have one hurdle but two. We have the hurdle of making sure our old code works with the new build. Then we have an additional larger hurdle that will take longer time of learning new functionalities from MQL5. Let's not kid ourselves: MQL4 above 509 is an entirely different language from MQL4 build 509 and before. A much more complex language than MQL4 is. And for developers like me who have ONLY CODED in MQl4, we don't know what classes and the other new terms mean. We don't necessarily code other languages or for Microsoft.