Marble/GeoData/PointerVsImplicitShare: Difference between revisions

Latest revision as of 17:44, 25 October 2016

This page is now on the community wiki.

@@ Line 1: / Line 1: @@
-Implicit sharing and storing objects as value is very reasonable for basic data as QStrings, but there are reasonable doubts regarding Placemarks and other GeoData.
+{{ Moved To Community }}
-There are some possibilities:
-* Don't use implicit sharing at all and store all objects on the heap with a pointer to it.
-* Use implicit sharing and storing as value for GeoDataCoordinates only.
-* Use implicit sharing and storing as value for all GeoData classes.
-To find out which is the wisest I try to look at every single class: