Errors, bugs, questions - page 1047
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
New this button, with the display of news in friends' feeds. Even if you turn off "show in feed", it still lights up when a news item from an already disconnected one appears.
At the very least, you need to set for max bars in the *requires terminal restart window
it's a lot of code to work with...
MQ Demo server.
In settings - max. bars per window = 100000
Yeah, right, tried that, got that "oops" - pure bug, for a service desk.
So (as I understand) innocent, unsuspecting indicator is called with rates_total==100000, but request CopyRates(,,100000,) leads to a pop (array out of range in ...) - the terminal already has only 50000 available.I also remembered.
When I was told in three pages that Bars was working fine. I switched max bars without a second thought and tried to check. Since I didn't see the connection, I didn't write that without reloading the terminal I was making it all up...
I don't use Bars, but maybe that was the hitch. Because I couldn't reproduce it the next day. And just didn't go into the settings anymore, I've always got unlimited.
It's just for developers, may be useful.
I also remembered.
When I was told on three pages that Bars were fine. I switched max bars without a second thought and tried to check. Since I didn't see the connection, I didn't write that without reloading the terminal it was all composed...
I don't use Bars, but maybe that was the hitch. Because I couldn't reproduce it the next day. And just didn't get into settings anymore, I always have unlimited.
It's just info for developers, may be useful.
I don't use regular prev_calculated for a long time, I declare globally prev_calc and count with it (I live happily and am very fat :)
Although, of course, this bug must be fixed. At least if rates_total did not change, then reset prev_calculated to zero, but if changed to a smaller value, then you must.
I don't use regular prev_calculated for a long time, I declare globally prev_calc and take it into account (I live happily and am very fat :)
...
Thanks, that's for the documentation :)
Thank you, that goes in the documentation :)
It's at ServiceDesk.
They've already been told everything.
You're just too mature a programmer to appreciate the value of your advice. For me, as an eternal dummie - this is on the verge of discovery :) so into the (personal) documentation.
They have already been told everything.
You're just too old a programmer to appreciate the value of your advice. For me, as an eternal dummie - this is on the verge of discovery :) so in the (personal) documentation.
Well, in your personal documentation, then, there's this.
Forced start of recalculation if history was trimmed to maxbars in window and rates_total became less.
The error is not critical (it will be corrected on the next tick), but on the same tick where the history was trimmed there will be a shift of the graph due to mismatch and recalculation will be blocked by the cycle condition because prev_cal>rates_total and it means there will be no entry into the cycle.
Well, in the personal documentation, then, there's this.
Forced start of recalculation if the history was trimmed to maxbars in the window and rates_total became less.
The error is not critical (it will be corrected on the next tick), but on the same tick where the history was trimmed there will be a shift of the graph due to mismatch and recalculation will be blocked by cycle condition because prev_cal>rates_total and therefore there will be no entry into the cycle.
Ok, thanks.