Discussion of article "Custom presentation of trading history and creation of report diagrams" - page 3
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
Try replacing the DealHistoryGetter.mqh file with the one attached to this post.
Only this error remains
You have the contract volume set to zero for some reason. If I am right, there should be 2 iterations before this error. But if I'm right, I can't imagine why the contract volume could be equal to zero, it doesn't happen....
Breakpoint at 451 and 461 and look through inputParam.deals[i].volume and the contracts array.
You have the contract volume set to zero for some reason. If I am right, there should be 2 iterations before this error. But if I'm right, I can't imagine why the contract volume could be equal to zero, it doesn't happen....
I don't know how to use the debugger, I put points, ran it, but there are no errors there.
Maybe the point is that there are such operations in the history?
Also on line 407 it would be good to put a breakpoint. and look at the lotArr array.
I will not reproduce your problem because it is related to your trading history. My histories (the ones I ran through this class) did not produce such errors....
It would also be good to put a breakpoint on line 407. and look at the lotArr array.
I will not reproduce your problem because it is related to your trading history. My histories (the ones I ran through this class) did not produce such errors....
Did you test on a real account or on a demo account?
Did you test on a real account or on a demo account?
It's not about the account, it's about your history. The terminal generates history in the same way for both real and demo accounts.
Perhaps there is a flaw in my class, but I can't reproduce it.... It's related to your history and, consequently, to your terminal and your trading account. Maybe there are some nuances in the analysis of the Me5 history that I missed when writing this class, but only you can reproduce it. I will have to deal with the debugger.
If you write more specifically what and where to look and write, I will help you to find the error.
It's not about the account, it's about your history. The terminal generates history in the same way for both real and demo.
There are no corrections on the demo, the screenshot of which I have given above.
Every day starts with them.