Scripts: sHistoryExport - handy script to export the historical data in the МТ4 format - 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
The whole depth of the story is a bit of a myth.
What does my script have to do with it?
This issue has been hotly discussed many times, but neither the script nor the terminal have anything to do with it. All claims - to the broker.
All in all - not bad: user-friendly interface, everything you need is there. But the script is very cumbersome: a lot of unnecessary code, and even for such a simple functionality to pull 2 libraries.
komposter hint how to make it so that when saving D1 the current day is written too?
komposter hint how to make it so that when saving D1 it writes the current day too?
Replace > with >= in this loop:
Then the 0th bar will be written as well.
Replace > with >= in this cycle:
Then the 0th bar will be recorded as well.
Great, thanks.
I remember the cycle, I don't remember what to change... almost broke :-)
hi...
help me, please.
sHistoryExport - a handy script for exporting historical data in MT4 format:
Author: Andrey Khatimlianskii
You say that the script also checks quotes. What is the check? Does it look for holes?
I downloaded the whole history of m1 from the demo server of Metaquotes and then compared the number of bars on my working timeframe m15 - 97 pieces are missing (
The script works well, but ... Will I have to manually search and "glue"?
You say that the script also checks quotes. What does it check? Is it looking for holes?
I downloaded the entire m1 history from the Metaquotes demo server and then compared the number of bars on my working timeframe m15 - 97 pieces are missing (
The script works well, but ... Will I have to manually search and "glue"?
Not all bars are on M1. And there's nowhere to pump them up.
What do you mean, there's no normal history in nature??? Well, it's come to this...
In principle, I would be satisfied with m5 as well, since the working timeframe is m15+, but nobody "officially" keeps m5, right?
By the way, you didn't answer about checking. Maybe you can tell me how to at least detect ALL the holes in order to orientate whether it is possible to do something with them (e.g., even manually patch small ones). I once encountered a check script with inbuilt "patching" by several algorithms. I don't see anything like that now. How do they test now? Why does no one care about holes? Somehow robo-owners get out of it...?