| Application preferences |
| Locator application preferences are set in the startup XML file. Preferences control product features and functionality. The <prefs> tag contains several attributes that may be modified, added or omitted. Table 3.3a below describes attributes and values for the application preferences. |
| MT1207 Application |
<prefs> |
|
| Attribute | Values / Range | Default 1 | Notes |
| diagnostics |
off, on |
on |
5 |
| postcode_source |
off, pcdxml |
off |
3 |
| locations_data_dir |
directory path |
|
2 |
| postcode_data_dir |
directory path |
|
2 |
| modules_dir |
directory path |
|
2 |
| results_max |
10 to 100 |
30 |
4 |
| Notes |
- Default value persists if attribute is omitted from tag.
- Relative path to locations, pcd, or modules folder. Include the forward slash such as "locations/".
- Se to "pcdxml" to allow searching by distance from a zip code.
- Controls the number of results returned to the module handling search results.
- Set diagnostics to "off" once system is fully configured, tested, and activated.
|
|
| Table 3.3a Tag Reference |
|
| |
<prefs
diagnostics="off"
postcode_source="pcdxml"
locations_data_dir="locations/"
postcode_data_dir="pcd/"
modules_dir="modules/"
results_max="20
/> |
| Figure 3.3b Example preferences |
|
| |
| |
| |
| Module Preferences |
| Module preferences should not be confused with application preferences as described above. Module prefs are set within the <loadmodule> tags and activates a module when loaded. See section 3.5 for setting module preferences. |
