I don't want confrontation either. I don't want it terribly. But sometimes confrontation turns out to be the only means that brings the parties (yours and ours) into a kind of sobering state.
Let's work. Sorry for the abruptness. I hope for your cooperation.
I'll take it. Thank you for being constructive.
P.S.
Taking advantage of the opportunity, please clarify: Is it necessary to check the return result of the HistoryOrderGetTicket andHistoryDealGetTicketfunctionsfor non-zero? And if so, why this is not mentioned explicitly in the documentation?
I hope Sergeyev not ban me. Honestly, I am not trolling. :)))
Accepted. Thank you for the constructive feedback.
P.S.
Taking the opportunity, please clarify: is it necessary to check the return result of the HistoryOrderGetTicket andHistoryDealGetTicketfunctionsfor non-zero? And if so, why this is not mentioned explicitly in the documentation?
I hope Sergeyev not ban me. Honestly, I am not trolling. :)))
There is no such thing as a zero ticket. Let's put it in the documentation.
You are saying that the ticket cannot be 0. I understand your position. Answer my question, how do you know that? Why can't a ticket equal 0? There is no explicit indication of this in the documentation.
I don't understand, it's like we're on the second page talking in different languages.
The graphical elements of the terminal are surprising.
After removing the indicator, a couple of minutes pass and only the chart is removed from the terminal. And there is also something wrong with the bar chart, it disappears altogether. It seems that resources of the terminal are not sufficient for calculation per each tick and the chart is not dealt with, it is deleted only. There is no such a problem in 4.
Does the storage work at all? If so, there are obvious problems with authorisation. You need to handle the authorisation problems.
The graphical elements of the terminal are surprising.
After removing the indicator, a couple of minutes pass and only the chart is removed from the terminal. And something also happens to the bar chart, it disappears altogether. It seems that resources of the terminal are not sufficient for calculation per each tick and the chart is not dealt with, it is deleted only. There is no such a problem in the Quartet.
...
What do you do with graphical elements? Give me an example of code for the test.
And during initialization I just assign a value to the buffer
x[i]=a;
1800 bars at once at every tick, I didn't test it, but the very fact that the histogram is not displayed is not quite normal. There is no such a problem in 4.
Allow the use of cookies to log in to the MQL5.com website.
Please enable the necessary setting in your browser, otherwise you will not be able to log in.
You are signed in. Two-factor authentication has been disabled. Set it up again and scan a new QR code, or continue with two-factor authentication disabled.
voix_kas
About the demotivators you wrote first.
I don't want confrontation either. I don't want it terribly. But sometimes confrontation turns out to be the only means that brings the parties (yours and ours) into a kind of sobering state.
Let's work. Sorry for the abruptness. I hope for your cooperation.
I'll take it. Thank you for being constructive.
P.S.
Taking advantage of the opportunity, please clarify: Is it necessary to check the return result of the HistoryOrderGetTicket andHistoryDealGetTicket functionsfor non-zero? And if so, why this is not mentioned explicitly in the documentation?
I hope Sergeyev not ban me. Honestly, I am not trolling. :)))
Accepted. Thank you for the constructive feedback.
P.S.
Taking the opportunity, please clarify: is it necessary to check the return result of the HistoryOrderGetTicket andHistoryDealGetTicket functionsfor non-zero? And if so, why this is not mentioned explicitly in the documentation?
I hope Sergeyev not ban me. Honestly, I am not trolling. :)))
There is no such thing as a zero ticket. We'll put it in the documentation.
You're not hearing me again.
You are saying that the ticket cannot be 0. I understand your position. Answer my question, how do you know that? Why can't a ticket equal 0? There is no explicit indication of this in the documentation.
I don't understand, it's like we're on the second page talking in different languages.
https://www.mql5.com/ru/docs/trading/ordergetticket
Returned value
Value ofulong type. In case of unsuccessful execution returns 0.
https://www.mql5.com/ru/docs/trading/ordergetticket
Returned value
Value ofulong type. In case of unsuccessful execution it returns 0.
The question was not about OrderGetTicket, but about HistoryOrderGetTicket and HistoryDealGetTicket. The question has already been solved.
The graphical elements of the terminal are surprising.
After removing the indicator, a couple of minutes pass and only the chart is removed from the terminal. And there is also something wrong with the bar chart, it disappears altogether. It seems that resources of the terminal are not sufficient for calculation per each tick and the chart is not dealt with, it is deleted only. There is no such a problem in 4.
Does the storage work at all? If so, there are obvious problems with authorisation. You need to handle the authorisation problems.
The graphical elements of the terminal are surprising.
After removing the indicator, a couple of minutes pass and only the chart is removed from the terminal. And something also happens to the bar chart, it disappears altogether. It seems that resources of the terminal are not sufficient for calculation per each tick and the chart is not dealt with, it is deleted only. There is no such a problem in the Quartet.
...
And what do you do with graphical elements? Give me an example of code for the test.
Nothing really.
When deinitializing, I delete
And during initialization I just assign a value to the buffer
1800 bars at once at every tick, I didn't test it, but the very fact that the histogram is not displayed is not quite normal. There is no such a problem in 4.