@@ -45,6 +45,7 @@ namespace pal
45
45
* Individual label providers may create subclasses of QgsLabelFeature in order to add
46
46
* more data to the instances that will be later used for drawing of labels.
47
47
*
48
+ * @note this class is not a part of public API yet. See notes in QgsLabelingEngineV2
48
49
* @note added in QGIS 2.12
49
50
*/
50
51
class CORE_EXPORT QgsLabelFeature
@@ -241,6 +242,7 @@ class QgsLabelingEngineV2;
241
242
*
242
243
* Implementations also take care of drawing the returned final label positions.
243
244
*
245
+ * @note this class is not a part of public API yet. See notes in QgsLabelingEngineV2
244
246
* @note added in QGIS 2.12
245
247
*/
246
248
class CORE_EXPORT QgsAbstractLabelProvider
@@ -342,6 +344,13 @@ Q_DECLARE_OPERATORS_FOR_FLAGS( QgsAbstractLabelProvider::Flags )
342
344
* engine.run( context );
343
345
* \endcode
344
346
*
347
+ * @note this class is not a part of public API yet. The provider's interface still
348
+ * uses pal::LabelPosition as an argument in drawLabels() method - this should be
349
+ * sorted out first (a class common to API and pal?). Also, the API may need more
350
+ * polishing to be easy to use - e.g. use concept of labeling layers in API
351
+ * (equivalent of pal::Layer) instead of subProviders(), label providers integrated
352
+ * into feature loop vs providers with independent feature loop), split labeling
353
+ * computation from drawing of labels, improved results class with label iterator).
345
354
* @note added in QGIS 2.12
346
355
*/
347
356
class CORE_EXPORT QgsLabelingEngineV2
0 commit comments