![MQL5 - Language of trade strategies built-in the MetaTrader 5 client terminal](https://c.mql5.com/i/registerlandings/logo-2.png)
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
Whoever says that shorting is not enough, let him be the first to throw at me at least one example (whether from the stock market or forex).
Why just forex? The platform is not just for forex symbols.
It is understandable that developers use a similar transformation of the original structure before compressing the data to transmit the story, which results in a huge compression ratio. But the fact remains that even if you do nothing, nothing at all, the worst you can get is an extra 65%.
In general, I would offer such structure as an internal one (with access from mql). For the beginning, allow to download such a story to the tester and then promote it in the terminal. The structures could exist in parallel for some time, which greatly simplifies the implementation. Conversion from the second of two structures to the first - without loss of information. Don't use the reverse, or build by simplified rules (like "asc_bar = bid_bar+spread).
And many, many satisfied clients...
And many, many satisfied customers...
Catch the axe - May 6, 2010.
Easily caught. even if per minute: 600 pips for shorts - yikes! they are two-byte (range -32768..+32767)
:)
MetaDriver:
Easily caught. even if per minute: 600 pips for shorts - whew! they are two-byte (range -32768..+32767)Easily caught. even if per minute: 600 pips for shorts - yikes! they are two bytes (range -32768..+32767)
:)
1. the axe should be more sophisticated, more than 0.32767 on a five-digit symbol, which is feasible for a week.
2. it is unlikely for minutes, but the candlestick storage format should be the same for both minutes and weeks
1. not really. if the base relative to other prices is not fixed by retarded standards,
then the range of coverage is double = [-0.32768 . . . +0.32767] total = 0.65536 (including the base itself)
2. This is more convincing, but it's all solvable. If you wish. I do not insist on exactly this structure. I think the principle of economy is clear, it is the most important thing.
Or here's an option:
Exceeding the standard structure by 8% (weighs 52 bytes), 65536 ticks. I doubt there is such a spread anywhereOr here's an option:
Exceeding the standard structure by 8% (weighs 52 bytes), 65536 ticks. I doubt there is such a spread anywhere