How do I move the global variable structure in the indicator when moving to another timeframe? - page 4
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
Personally, I use resources via union.
Could you elaborate on that. Thank you.
Can you elaborate on that? Thank you.
I'll write it down in the Buy More sometime.
Actually, here is the class for it.
And you just need to add two lines to the indicator:
I'll write it down in the QB sometime.
Actually, here's the class for it.
And in the indicator you only need to add two lines:
Thanks, that's all on point.
In fact, here's the class for it.
At first sight, implementation of the T[]<->uint[] conversion is not optimal.
wrote this code a long time ago. It may be.
There is nothing much to optimize there though. Maybe only in some small things.
Anyway, this class can be tried in my latest free product in the Market.
I would be grateful if you could suggest a better implementation.
I would be grateful if you could suggest a better implementation.
Forum on trading, automated trading systems and trading strategy testing
Libraries: TradeTransactions
fxsaber, 2019.03.15 07:36
How to transfer a global variable, structure, object in an indicator when moving to another timeframe? Googled it and couldn't find it.
Forum on trading, automated trading systems and testing trading strategies
Libraries: TradeTransactions
fxsaber, 2018.12.17 23:48
You can trade anything through Resources.
Not, unfortunately, a barefaced one. I won't go into your bibles.
I've already tried to look into your code and realized I'm not mature enough. :))
Anyway, if you open all the inluders, your code will be longer in source code and executable.
Also, a couple of times burned, when I used your libs, and then found the source of brakes for a long time, until they were torn down. After that I gave up.
Main difficulty of using your code, which consists of many inludes, is high complexity of debugging, when at each step new class, defines or macros.
And I spare time for the test, because I understand that it is hardly possible to speed up my algorithm considerably.
The only one bug I see now is using loops instead of CopyArray in some places. After this fix my code will be almost perfect in terms of performance and readability.
The only bug I see now is that I use loops in some places instead of CopyArray. After this fix my code will be almost perfect in terms of performance and readability.
If you write a performance measurement, it would be interesting to compare.
:)
It's strange that no one writes about "crutches", "reinvention of a wheel", "difficulties of data transfer to another terminal","the problem must be solved by MQL means "...
It turns out that solutions based on metaquotes are crutches and mauvais ton)