The agony of choice - page 2
You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Come on!!! :) I used to have a program that worked fine, was being tweaked. And then, bang, 600 builds came out. And it makes no difference - whether I had or hadn't sawn it before - metadata changes occurred and at that very moment, both sawn and un-peeled programs that used the modified data stopped working all at once! And it didn't matter if it was mine or someone else's.
Don't be misled. The switch to 600+ took place a long time ago.
Many indicators are simply not supported by those who developed them. Correspondingly, users must recompile for new builds. And if you don't fix compilation errors it will be very difficult for an uninformed person to do that - I don't need to tell you about it. That's what I mean. For example, I can send the author the Expert Advisor's code and let him try (at least within a month) to fix the errors :)
Not true at the very least. If you are a programmer and you write code, it is usually recompiled at least once a month. There is always development of programs, adding features or polishing.
Nothing happens "suddenly" - there is another situation - you have been asleep for a year or two and then "suddenly". You need to keep an eye on your programs and you won't have any problems.
yeah, right.... check, compile and rewrite if necessary once a month or even more ... what the hell??? I have a dozen programs on my D drive from the fourth year, with WinXP 32 bit, and they still work on Win 8.1 64 bit, without reinstalling every time I reinstall the system and after the next update mastdaya ....
mmmoguschiy:
This is not nonsense but a statement of fact. Some of the indicators and EAs available have stopped working. Some of them I have fixed, some of them I am too lazy to bother with.
Be careful... Now you will be asked for the codes that confirm such claims. Otherwise, they will accuse you of misrepresentation, of minute-by-minute changes in your statements, and of incompetence in everything, including that in which no one is more competent than you.
That's the point which is 600+. Everyone knows what I mean. and so do you. And yes - I'm not talking about yesterday.
Many indicators are simply not supported by those who developed them. Correspondingly, users must recompile for new builds. And if you don't fix compilation errors it will be very difficult for an uninformed person to do that - I don't need to tell you about it. That's what I mean. For example, I can send the author the Expert Advisor's code and let him try (at least within a month) to fix the errors :)
the easiest solution for the user is to find an old build and compile on it
and everything will work on new builds if someone doesn't play a joke on April 1st)
the easiest solution is for the user to find an old build and compile on it
and everything will work on new builds unless someone plays a joke on April 1)
the easiest solution for the user is to find an old build and compile on it
and everything will work on new builds unless someone plays a joke on April 1)
Honestly this is a revelation to me. How can an old tool work without errors on a system with modified metadata? It simply will not understand them at best. At worst it will freeze. Or it works "for the time being". But I will try it today for sure.
They canceled the jokes, didn't they? People are against jokes!
Honestly, this is a revelation to me. How can an old turntable work without errors on a system with changed metadata? It simply won't understand them at best. At worst it freezes. Or it works "for the time being". But I will try it today for sure.
so the old car is still going.