[Qgis-developer] DataCustomProperties store labeling field by their id's and not names
haubourg
regis.haubourg at eau-adour-garonne.fr
Fri Aug 10 05:32:45 PDT 2012
Hi all, (again)
DatacustomProperties for labelingfields ( New generation labeling ) are
stored as follow in qgs projects or qml style :
<customproperties>
<property key="labeling" value="pal"/>
<property key="labeling/dataDefinedProperty0" value="27"/>
<property key="labeling/dataDefinedProperty1" value="29"/>
<property key="labeling/dataDefinedProperty10" value="24"/>
<property key="labeling/dataDefinedProperty11" value="25"/>
<property key="labeling/dataDefinedProperty12" value="26"/>
<property key="labeling/dataDefinedProperty2" value="30"/>
<property key="labeling/dataDefinedProperty3" value="33"/>
<property key="labeling/dataDefinedProperty4" value="31"/>
<property key="labeling/dataDefinedProperty5" value="28"/>
<property key="labeling/dataDefinedProperty6" value="32"/>
<property key="labeling/dataDefinedProperty9" value="23"/>
<property key="labeling/enabled" value="true"/>
<property key="labeling/fieldName" value="LblField"/>
<property key="labeling/fontSize" value="8"/>
<property key="labeling/multiLineLabels" value="true"/>
</customproperties>
Everywhere else in QGIS projects are identified by their names, and that is
great because projects are much more stable this way. If a user (or a
program like GDAL and GML) changes fields order in data source, all custom
properties get mixed up, in a very 'Mapinfo'-like behaviour.
Is it feasable to have custom properties identified by name (for the
future) or id's (to make QGis compatible with old Qgs)?
Is that a feature request I have to create?
All the best
Régis
--
View this message in context: http://osgeo-org.1560.n6.nabble.com/DataCustomProperties-store-labeling-field-by-their-id-s-and-not-names-tp4994392.html
Sent from the Quantum GIS - Developer mailing list archive at Nabble.com.
More information about the Qgis-developer
mailing list