The XML Schema Definition file of the configuration xml can be downloaded from this link.
With the help of the XSD file, you can validate your configuration before applying it to the MarvinSketch application. You can also find information about the usable elements, and attributes in the documentation sections of the definition file.
The default configuration becomes active when no user configuration is found. If a user configuration file is in the [.]chemaxon directory inside the home directory of the user with the name "AttachDataDialog.xml" can be found, then the configuration defined in the file will be used, and the default configuration will not take effect.
Contents of the default configuration:
<?xml version="1.0" encoding="UTF-8"?>
<AttachDataDialogConfig
xmlns="AttachDataDialogConfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="AttachDataDialogConfig AttachDataDialogConfig.xsd ">
<context name="Atom"></context>
<context name="Bond"></context>
<context name="Single Bond"></context>
<context name="Double Bond"></context>
<context name="Fragment"></context>
<context name="Group" displayName="Group (Selection)">
<dataname textRepresentation="COEFF"/>
<dataname textRepresentation="Stoichiometry"/>
<dataname textRepresentation="[DUP]"/>
<dataname textRepresentation="REAGENT"/>
</context>
</AttachDataDialogConfig>
<?xml version="1.0" encoding="UTF-8"?>
<AttachDataDialogConfig
xmlns="AttachDataDialogConfig"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="AttachDataDialogConfig AttachDataDialogConfig.xsd ">
<context name="Atom">
<dataname textRepresentation="foo" defaultTag="f" multipleValuesEnabled="false" valueFieldEditable="false">
<value>bar1</value>
<value>bar2</value>
<value>bar3</value>
<unit>u1</unit>
<unit>u2</unit>
</dataname>
<dataname textRepresentation="foo2" multipleValuesEnabled="true">
<value>bar2</value>
<value>bar4</value>
<unit>u1</unit>
<unit>u3</unit>
</dataname>
</context>
<context name="Group" displayName="Group (Selection)" nameFieldEditable="false">
<dataname textRepresentation="foo">
<value>bar3</value>
<value>bar4</value>
<value>bar5</value>
<unit>u1</unit>
<unit>u3</unit>
<unit>u4</unit>
</dataname>
</context>
<context name="Bond"/>
<context name="Single Bond">
<dataname textRepresentation="foooo"/>
</context>
</AttachDataDialogConfig>
The result of this configuration can be seen in the dialog.
With this file the following have been configured:
The context field will have four values: the Atom, Group, Bond, Single Bond
When the Atom context is selected, the Name combo box will have the following values set: editable empty field, foo, foo2
When the Atom context is selected, and the value foo is selected in the Name combo box, the Value field will not be editable
When the Group context is selected, the Name combo box will have the following value set: foo
When the Group context is selected, the Name combo box will not be editable
When the Bond context is selected, the Name combo box will only contain the editable empty field
When the Single Bond context is selected, the Name combo box will have the editable empty field, and the foooo name set
In one session if the user enters something into the editable empty field, then that value will be added to the list of names belonging to the context. These values will be missing after restarting the application.
Same names in the name field are independent from each other, if they are in a different context. Same names inside the same context will cause confusion, and maybe malfunction.
After selecting the name, the Value field will load the defined values in the given Context for the specified name, if there are any.
If the multipleValuesEnabled attribute of the namedata element is set to true, then the user can select more than one value in the Values field, otherwise only one value can be selected.
If the defaultTag attribute is set for the dataname element, and the name is selected, then the Tag field will be filled with its defaultTag. (Tag can be of a single character length, this is only checked by the GUI.)
The Values field also has an empty editable field, newly entered values work the same as by the Name field.
The Unit field also has an empty editable field, newly entered values work the same as by the Name field.