
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
-Alexey-:
Это было бы логично, но сейчас операция ">" ("<" не проверял) может возвращать результ true для таких чисел "равных в смысле машинного нуля". Обнаружился эффект т.к. результат численного расчета получился больше теоретически возможного в результате такого эффекта, а после использования спец. функций, что выше - стал правильным. Поэтому и предлагаю ввести дополнение в справку.
My knowledge of the subject is superficial, so I can't assess what you have said. Write to Service Desk and they will look into the matter.
Developerc - Thanks for the work done - mt5 is a good tool,
I would like to add more examples of working with functions,
classes etc. Of course to do it in the help - ideal, but here too
But here it would be good.
A special thanks to those who write articles with examples. Thank you very much.
For now, take this file as an example.
The CSignalCustomMACD class is absolutely identical to CSignalMACD, except for the fact that it is based on the "custom" version of the indicator from the standard delivery.
Do not forget to add a line in the source code of the Expert Advisor:
otherwise it will not work in the tester.
If the folder Indicators\Examples does not contain the MACD.ex5 file, the indicator should be compiled.
An example will be added to the help in the nearest future.
This would make sense, but now the operation ">" ("<" didn't check) may return true for such numbers "equal in the sense of machine zero". The effect was detected because the result of the numerical calculation was larger than theoretically possible as a result of this effect, but after using the special functions above it became true. That is why I propose an addition to the help.
Just use DBL_EPSILON in all comparisons, it's not difficult:
If you work with prices, normalise them after any calculations and use Point/2.0 instead of DBL_EPSILON:
For some reason, reading an array via the FileReadArray function doesn't work , although the file is opened, contains data, etc:
For some reason, reading an array via FileReadArray function doesn't work , although the file is opened, contains data, etc.:
You first write data to the file in the same way, see the format...
And then read...
You first write the data to a file in the same way, see the format...
And then read...
I write data one line at a time in OnCalculated indicator or OnInit of the Expert Advisor via FileWrite.
As a result, the file is a list of numbers:
10000
10000
9996.85
10005.25
10023.4
10029.7
Of course, we could write the array as a whole too, but why should we make unnecessary steps and what is the error here?
I couldn't find any restrictions on this in the documentation.
I write data line by line to OnCalculated indicator or OnInit of Expert Advisor via FileWrite.
As a result, the file is a list of numbers:
10000
10000
9996.85
10005.25
10023.4
10029.7
Of course, you can also write the array as a whole, but why do I need to do unnecessary things and what is the error here?
I did not find any limitations concerning this subject in the documentation.
For some reason, reading an array via the FileReadArray function doesn't work , although the file is opened, contains data, etc:
From the help:
FileReadArray
Reads arrays of any type, except string arrays (can be an array of structures containing no strings and dynamic arrays), from a binary file from the current position of the file pointer.