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
The problem is most likely in something else. I have the exact same array decl aration in OnInit() worked fine and still works. You have an omitted Latin letter m in the name of the ArrSybols array. Maybe this is a programmer's problem?
It may be missing, but does it make any difference?
And if I write it in native (which is not forbidden, as I understand it) the whole terminal should crash?
The code works exactly without such array declaration, even if you just specify the dimensionality everything works.
The original array declaration was like this
The question is still valid.
I have managed to attach the indicator in a separate window to OBJ_CHART, but when I change the size of the indicator window, it is not very nice, because if the height of OBJ_CHART is 500, then the height of the indicator window has been set to maximum 493. As a result, it leaves you with an ugly top. How to get rid of it?
Code:
It may have been missed, but does it make a difference?
Of course it does. I don't have to explain it to you :) If an array is defined with one name, but the elements of this array are called with a different array name, then... :)
If everything works without initialization of the array manually, you should look at the code, as you yourself understand. After all, the absence of explicit string-array initialization doesn't prevent the client terminal from initializing this array by itself.
I repeat: such a string worked and still works out "to the best of its ability".
Of course it does. I don't have to explain it to you :) If an array is declared with one name, but the elements of this array are accessed with a different array name, then ... :)
If everything works without initialization of the array manually, you should look at the code, as you yourself understand. After all, the absence of explicit string-array initialization doesn't prevent the client terminal from initializing this array by itself.
I repeat: such a string worked and still works.
No, no, the problem is not in the name, it's that the array is filled with an enumeration during declaration.
It works well with all the types except for strings. With strings it really crashes any program (expert or script is not important).
This is an obvious bug write to servicedesk.
This is how it works:
but if you uncomment the string array declaration, it doesn't work.
Check the maximum number of bars in the window in the settings
Renat, another wild taffy, are you sure you found the error?
The traffic problem is solved, but the thing is that we haven't released the server components in liveupdate yet. So far the client terminal updates have been released and the servers will be in the next update. They have not been tested yet.
Last build (430) when testing with Forward period and Custom Max - hangs (seems to be at the moment of switching to Forward testing). At first I blamed it on my Expert Advisor, but then I checked the following code:
I have set parameters to optimize from 1 to 1000, all ticks, USDCAD, M4 from 01.01.2011 to today (with Forward - any period). Freeze. Disabled remote agents - I restarted the terminal - it hangs too. Removed the forward period - it works. Whether Custom Max is to blame - didn't check it. Before this build - everything worked.
What does it mean?
2011.04.17 15:21:22 Tester tester agent failed