ASCII Mapping: Difference between revisions
From MultiCharts
no edit summary
No edit summary |
No edit summary |
||
Line 2: | Line 2: | ||
In such a case ASCII mapping is the solution; there are two principal reasons for using ASCII mapping: | In such a case ASCII mapping is the solution; there are two principal reasons for using ASCII mapping: | ||
# If one or several ASCII files constantly used are periodically updated. Even if there are just a few updates per day, re-importing hundreds of symbols is difficult or just not feasible; | # If one or several ASCII files constantly used are periodically updated. Even if there are just a few updates per day, re-importing hundreds of symbols is difficult or just not feasible; | ||
# If tick/volume bars must be displayed on a chart. | # If tick/volume bars must be displayed on a chart. | ||
<br> | |||
When mapping, the file path and format are indicated once, and every time a chart is created the program finds the file automatically, converts it into the necessary format based on the preset configuration and displays the data. | When mapping, the file path and format are indicated once, and every time a chart is created the program finds the file automatically, converts it into the necessary format based on the preset configuration and displays the data. | ||
<div | <div class="note">ASCII Mapping file reference details are displayed under the '''"ASCII Mapping" tab''' in the '''Edit Symbol''' window (see [https://www.multicharts.com/trading-software/index.php/Setting_Properties#Editing_an_Existing_Symbol_Properties here]). This tab is displayed only when an instrument is mapped to a file.</div> | ||
<br> | <br> |