Changed file format to be able to save settings and data together.
Old settings files still can be imported. Data export will also contain
settings, so we always have the system settings with the system state.
Sample file:
<!DOCTYPE UAVObjects>
<uavobjects>
<version>
...
</version>
<data>
<object id="0xC409985A" name="AccessoryDesired">
<field values="0" name="AccessoryVal"/>
</object>
...
</data>
<settings>
<object id="0xF2875746" name="ActuatorSettings">
...
</settings>
</uavobjects>
Changed the UAV import of saved settings to not pull in invalid enum
values. Will warn on the dialog that an element of the UAVObject was
invalid and turn off the "save" checkbox. Also will send a qDebug output
showing the UAVObject name and the invalid enum value.
This menu option is useful for technical support. It exports all
current UAV data objects to the XML, similar to settings. This data
can't be imported (it is useless), but can be published or passed to
the tech support for troubleshooting.
INI file format is to be used for compact export to publish on forums, etc.
git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@2866 ebee16cc-31ac-478f-84a7-5cbb03baadba
UAV Settings files (*.uav) now include option lists for enum fields.
Simple XML files (*.xml) contain only subset of fields (name and values).
git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@2865 ebee16cc-31ac-478f-84a7-5cbb03baadba
This plugin registers itself in the GCS File menu and allows to save the settings database (all UAVObjects which have settings flag set) into an XML file. No import function is implemented yet, but the XML is human-readable and can be used to enter values by hand.
git-svn-id: svn://svn.openpilot.org/OpenPilot/trunk@2781 ebee16cc-31ac-478f-84a7-5cbb03baadba
