Registered Member
|
Do I understand it correctly that GeoDataTreeModel only shows the structure of the kml-data,
but not all the data and if one has something like:
one can only exract the coordinates of the LinearRing by doing something like void FileReaderPositionProviderPluginPrivate::createSimulationPlacemarks( GeoDataContainer *container ) ? |
KDE Developer
|
The model contains both the structure and the data. The view (TreeView) only shows the structure though. I don't quite get the relation FileReaderPositionProviderPluginPrivate::createSimulationPlacemarks, can you elaborate on that?
|
Registered Member
|
Ok, maybe, I just did not understand QAbstractItemModel in order to deal with GeoDataTreeModel properly. Why FileReaderPositionProviderPluginPrivate::createSimulationPlacemarks ? In FileReaderPositionProviderPluginPrivate you load a kml file with placemarks but you do not use GeoDataTreeModel for this purpose. On the other hand in examples/cpp/kml-inspector/main.cpp you use GeoDataTreeModel . So I do not understand which is the better/faster way of dealing with kml files: parse a kml file as in FileReaderPositionProviderPluginPrivate or load in into GeoDataTreeModel as in examples/cpp/kml-inspector/main.cpp ? |
Registered users: Bing [Bot], claydoh, Google [Bot], rblackwell