The .xml format for scripting allows all the configuration settings to be defined within the file itself. This removes the need for separate .con files. However, it is not necessary to redefine your established settings in a new .xml script, as you can load existing .con files into a new .xml script.
You can load the settings from an existing .con file using the <load_options> tag in the .xml file. Insert the tag at the beginning of an .xml file before any variables are defined using the following format:
<load_options filename "xxxx.con"/>
where xxxx.con is the name of the file.
If the .con file is located, it is loaded into the script. The options defined in the .con file override the appropriate options in the .xml file. The script searches the following location for .con files:
C:\Users\Public\Documents\Autodesk\Shareddb
Example
This example demonstrates how a legacy .con file is used to redefine variable values without having to manually edit them.
A script contains a variable which defines whether electrode groups are copied:
<set name="options.group_copies">true</set">
If you edit the script to load a .con file which contained the entry group_copies:false, the value of %[options.group_copies] is automatically redefined as if the command <set name="options.group_copies">false</set> was included in the .xml.
With the direction customisable scripts are taking, we recommend you complete the following actions to future-proof your EDM file output: