MetaTrader 5 Python User Group - how to use Python in Metatrader - page 27
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
About python - recently talked about ranger (file manager), which is written in it. Used it for a few days, got impressions - cool concept with interesting features, but python really lags (if some complex tasks are performed in the background). Ripped it off, I don't know why people are so attracted to python. Putting a similar thing on C.
Every tool has its own purpose.
Use mc ...
Version 5.0.9 is available:
Thanks, ok.
Unclear behaviour when downloading quotes:
If uploaded from 2018, prices are uploaded and there is no error
History is available:
Unclear behaviour when downloading quotes:
If uploaded from 2018, prices are uploaded and there is no error
History is available:
Found a solution, put "max bars in window" of the terminal UnlimitedFor MT5CopyRatesXxx functions () we have specially added a note for such case
For the MT5CopyRatesXxx () functions we have specifically added a note for this case
super, thanks
It's written in the documentation:
Данные, полученные из терминала MetaTrader 5, имеют UTC-время.
Error: the module seems to return data in server time, not in UTC. (MT5CopyRatesRange)
In general, terminal stores time in what timezone? UTC or server time or local time of the terminal?
It's written in the documentation:
Error: the module seems to return data in server time, not in UTC. (MT5CopyRatesRange)
In general, terminal stores time in what timezone? UTC or server time or local time of the terminal?
The terminal server time is always returned, i.e. nothing needs to be corrected. The help would need to be updated.
The terminal stores in UTC+2 usually, by the clock in the "market overview" you can determine
The terminal servers always return in time, i.e. nothing needs to be corrected. The help would have to be updated.
The terminal stores in UTC+2 usually, you can tell from the clock in the "market overview"
This is inconvenient and wrong. Even just by looking in the terminal it is difficult to correlate the time there and somewhere else.
The local time is known , UTC is easy to calculate (I remember the offset) or to get. The server time on the other hand has to be found and compared to anything. What is the offset of the server time? The answer is usually +2, or watch. This is not convenient. In the terminal, too, I would like to set the time display (local, UTC, server time), it would be much more convenient.
And if the data from different terminals?
UTC is much better, we need to fix the functions , not the help.
This is inconvenient and wrong. Even just by looking at the terminal it is difficult to relate the time there to somewhere else.
The local time is known, UTC is easy to calculate (I remember the offset) or get. The server time on the other hand has to be found and compared to anything. What is the offset of the server time? The answer is usually +2, or watch. Uncomfortable.
UTC is much better, need to fix the functions , not the help.
Maybe for some purposes inconvenient, for me so far for the current convenient: what I see in the terminal, I get in python, do not have to bring to another range