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
So if you can't be bothered to read all the history back in time, then I don't see the problem. Find out the opening and closing times of each bar and look at the number of seconds in those intra-bar ranges. If less than expected, write a "fake" bar. This will be the tipping point, after which all other bars will be incomplete. There is no point in searching further.
Such "fake" bars can also be found in the middle of a "normal" story (in which case most of the practical story will be discarded), and even whole series of such bars. I am telling you that there is no reliable method.
Such "fake" bars can also occur in the middle of "normal" history (in which case most of the useful history will be rejected), and even entire series of such bars. I'm telling you, there's no reliable way.
Then the statistics should be done by looking out where the amount of "fake" bars is not occasional (read: accidental), but regular (constant), and most likely the pattern will not be simple: when several consecutive bars consistently have more than the Open - Close range, we can assume that this is not an accident and feel free to stick a ski stick in it.
There is no reliable - perfectly working - method, Forex is not reliable. There is only a common sense criterion to proceed: how many consecutive bars in a series must not correspond to the condition of the number of seconds to be considered not as an accidental "failures" in the history, but as the beginning of the preceding era - the era of less detailed history making.
There is no reliable - ideally working - way, Forex is not reliable at all. We can only use a common-sense criterion: how many consecutive bars in a series must fail to meet the condition of the number of seconds to be considered not as a random "failures" in the history, but as the beginning of the preceding era - the era of less detailed history keeping.
Have you worked on MT4? Have you encountered a similar problem? - There is no such a problem there, which means there is a reliable way, but it is in the developers' hands. I have already suggested one solution.
Another solution, expressed by tol64, is not to display incorrect data at all.
All other methods, but on the part of the user, will be unreliable.
Have you worked with MT4? Have you encountered such a problem? - There is no such a problem there, so there is a reliable way, but it is in the developers' hands. I have already suggested one solution.
Another solution, expressed by tol64, is not to display incorrect data at all.
All other tricks on the part of the user will be unreliable.
You can make an additional functionality at the language level that will return the quality of history in percentage for a certain pair and TF, for a certain period.
For example, analyze the minute history for the year/month, if it is not 100% then there will be problems.
Have you been working on MT4? Have you encountered a similar problem? - There is no such a problem there, which means there is a reliable way, but it is in the developers' hands. I have already suggested one solution.
The other solution, expressed by tol64, is not to display incorrect data at all.
All other methods, but on the part of the user, will be unreliable.
Gentlemen, can you give me a hint?
- There is a dll,
- I know it has the function fn(...),
How to know what type of parameters should be passed to it?
Gentlemen, can you give me a hint?
- There is a dll,
- I know it has a function fn(...),
How to know what type of parameters should be passed to it?
I'm still embarrassed to ask, although the question has been bothering me for a long time...
TheCopyTime copies directly into the buffer what is on the specified timeframe of the called indicator handle. I can be mistaken, but ideologically there is no programmatic algorithmic "slots", that could squeeze in the preliminary calculations of the primary refinement of date-time (we know that non-M1 timeframes have inaccurate time values). I would very much like to know how to defeat such a straightforward copying just through the above function.
Can you tell me in which cases the value of a tick may differ depending on whether the position is currently in profit or loss?
SYMBOL_TRADE_TICK_VALUE
SYMBOL_TRADE_TICK_VALUE_PROFIT
SYMBOL_TRADE_TICK_VALUE_LOSS