11 Commits

Author	SHA1	Message	Date
Nyall Dawson	01d34ede9d	Sip sync	2017-09-25 17:12:03 +10:00
Nyall Dawson	9e61cd63df	Move overriden methods from headers to cpp files ... Since they can't be inlined anyway	2017-09-19 17:22:33 +10:00
Nyall Dawson	bb425e4540	Cleaner signature for QgsAbstractGeometry::closestSegment	2017-09-19 17:22:33 +10:00
Nyall Dawson	54c988f918	Make QgsAbstractGeometry::toCurveType pure virtual, and implement ... for all geometry types Previously this method would return nullptrs for many geometry types	2017-09-19 17:22:33 +10:00
Matthias Kuhn	501081f863	Remove unrequired SIP_SKIP	2017-06-14 07:37:31 +02:00
Matthias Kuhn	37a306e3f2	Fix tests	2017-06-14 07:37:31 +02:00
Matthias Kuhn	96cf4b7026	Projecting a 2D point with inclination assumes 0 for Z	2017-06-14 07:37:31 +02:00
Matthias Kuhn	1808dc9c95	More intuitive QgsPoint python constructors ... In python, the wkb type of a QgsPoint will by default be determined from the provided parameters, where Z and M will be added as required if the wkbType is Undefined. QgsPoint(x, y, z=nan, m=nan, wkbType=QgsWkbTypes.Undefined) Thanks to the python API support of named parameters, it's also straightforward to specify z, m and wkbType in any desired combination. On the other hand, on C++ side it's often preferable to use QgsPoint(QgsWkbTypes::WkbType wkbType, double x, double y, double z, double m); due to the lack of named parameters which make it harder to specify a specific type and the advantage of typesafety that makes it possible to verload the first constructor with this one.	2017-06-14 07:37:31 +02:00
Matthias Kuhn	4db671e83b	Fix sip bindings for QgsPoint	2017-06-14 07:37:31 +02:00
Matthias Kuhn	7e487190e8	Add an easy to use Z/M default value constructor to QgsPoint	2017-06-14 07:37:31 +02:00
Matthias Kuhn	4eae0872ab	Fix QgsPoint(XY) sip bindings	2017-06-14 07:37:31 +02:00