User guide

Page 80

visualise | communicate | ENGAGE The InstantAtlas Designer

g the InstantAtlas Area Profile Template User Guide

Figure 96

You can find a full list of ActionScript functions in section ‘C.4.3.2. Button

Properties’.

C.5. Applying a Design to Other Dynamic Reports

It is simple to apply a custom design to a series of InstantAtlas reports that

you have published, even if the map and indicator data in each report is

different. All you need to do is replace the existing config.xml file of the

dynamic report you want to change with the config.xml file you have

customised using the Designer.

However, it is very important to realise that the configuration file is

template-specific. You can only apply the same config.xml file to multiple

dynamic reports if they were published using the same template.

For example, a series of dynamic reports published using the Single Map

(Flash Edition) v6.5.0 template can share the same config.xml file. But

applying this config.xml file to a dynamic report published using, for

example, a Double Map v6.5.0 template is not supported and will almost

certainly cause the report to malfunction.

Similarly, applying a config.xml file from a Flash dynamic report to an

HTML dynamic report will cause it to malfunction.

We also do not recommend re-using a config.xml file between minor

version changes e.g. applying a version 6.4.0 config.xml file to a 6.5.0

report. It might appear as if the report still works fine, however, you will not

be able to find configuration settings which are necessary for the new

functionality of the 6.5.0 report.

Customers of InstantAtlas can use the Configuration File Converter to

update older config.xml files to a newer version. This tool is available within

’My InstantAtlas’, the user restricted area of our website.

In the config.xml file of an HTML template, each component can be

toggled by a button without needing to change the properties of the

component. You simply need to insert a button with the relevant

JavaScript function (see section ‘C.4.3.2. Button Properties’).

However, you may want to define if the component is visible when

the report is opened using the property ‘Visible At Startup?’. You

may also want the component to disappear when you click outside it

with the mouse. This is done by ticking the box of the property

‘PopUp Window?’. A component which has this property ticked is

styled to show a drop shadow. Both properties are part of all report

components.