boolObjectCreate(
long chart_id, // идентификатор графикаstring name, // имя объектаENUM_OBJECT type, // тип объектаint sub_window, // индекс окнаdatetime time1, // время первой точки привязкиdouble price1, // цена первой точки привязки
...
datetime timeN=0, // время N-ой точки привязкиdouble priceN=0, // цена N-ой точки привязки
...
datetime time30=0, // время 30-й точки привязкиdouble price30=0// цена 30-точки привязки
);
Creates an object with the specified name, type and initial coordinates in the specified sub-window of the graph. You can specify up to 30 coordinates when creating it.
I.e. 30 is the maximum. So first comes an unknown number (N) of parameters and the very last parameter with index 30.
Creates an object with the specified name, type and initial coordinates in the specified sub-window of the graph. Up to 30 coordinates can be specified during creation.
I.e. 30 is the maximum. So first comes an unknown number (N) of parameters and the very last parameter with index 30.
Usually they write N, and after that they specify the maximum number N where N<=30
SZZ: they are masters of confusion: one change of indexation alone, when copying an array, costs nothing )
it turns out that the first coordinate of the trend line is not the first. but zero, and nowhere does it say that, at least where you can quickly find this information.
sanyooooook: you usually write N, and after that you specify the maximum N where N<=30
Not in this context. This is not a description of conditions, but a variable name. And the variable name should reflect the maximum allowable index. This is why the last variables go with index 30:
datetime time30=0, // время 30-й точки привязкиdouble price30=0// цена 30-точки привязки
Not in this context. This is not a description of conditions, but a variable name. And the variable name should reflect the maximum allowable index. Therefore, the last variables go with an index of 30:
In all maths textbooks they write it like I mentioned above, they specify N and then give this N a value not exceeding 30.
They've got it right in the reference in the quad:
boolObjectCreate(
long chart_id, // идентификатор графикаstring object_name, // имя объектаENUM_OBJECT object_type, // тип объектаint sub_window, // индекс окнаdatetime time1, // время первой точки привязкиdouble price1, // цена первой точки привязки
...
datetime timeN=0, // время N-точки привязкиdouble priceN=0// цена N-точки привязки
);
paladin800: I see. The problem is that the sandbox of terminals is located on drive C and even if I create a RAM-drive (e.g. drive E), I can't redirect sandbox there.
First of all, it is possible to redirect it.
And if you use WinAPI, you don't need to redirect either. Secondly, creation of files in memory has nothing to do with RAM-disks, though WinAPI is needed too.
I used Metaeditor's help to take an example of how to work with the spread. I ran it on GBPCHF, CADCHF where spread is not 1-2 pips. Can you tell me why the array is filled with zeros? Is it designed that way?
meta-quotes, you have me completely confused (
N after 30 first ?
30 max?
meta-quotes, you've got me completely confused (
N after 30 first ?
30 max?
The help specifies:
Creates an object with the specified name, type and initial coordinates in the specified sub-window of the graph. You can specify up to 30 coordinates when creating it.
I.e. 30 is the maximum. So first comes an unknown number (N) of parameters and the very last parameter with index 30.
The help specifies:
Creates an object with the specified name, type and initial coordinates in the specified sub-window of the graph. Up to 30 coordinates can be specified during creation.
I.e. 30 is the maximum. So first comes an unknown number (N) of parameters and the very last parameter with index 30.
Usually they write N, and after that they specify the maximum number N where N<=30
SZZ: they are masters of confusion: one change of indexation alone, when copying an array, costs nothing )
or this:
it turns out that the first coordinate of the trend line is not the first. but zero, and nowhere does it say that, at least where you can quickly find this information.
you usually write N, and after that you specify the maximum N where N<=30
Not in this context. This is not a description of conditions, but a variable name. And the variable name should reflect the maximum allowable index. This is why the last variables go with index 30:
Is there any way to make file operations write/read files not to disk but to RAM to work faster and without holes?
Not in this context. This is not a description of conditions, but a variable name. And the variable name should reflect the maximum allowable index. Therefore, the last variables go with an index of 30:
They've got it right in the reference in the quad:
You can make a RAM disk, you can create a file in memory.
I see. The problem is that the sandbox of terminals is located on drive C and even if I create a RAM-drive (e.g. drive E), I can't redirect sandbox there.
First of all, it is possible to redirect it.
And if you use WinAPI, you don't need to redirect either. Secondly, creation of files in memory has nothing to do with RAM-disks, though WinAPI is needed too.
I used Metaeditor's help to take an example of how to work with the spread. I ran it on GBPCHF, CADCHF where spread is not 1-2 pips. Can you tell me why the array is filled with zeros? Is it designed that way?