mirror of
https://github.com/qgis/QGIS.git
synced 2025-12-04 00:06:46 -05:00
Correctly render ordered list in maplayerrenderer API docs
This commit is contained in:
parent
77dc2bdde2
commit
ef232d5f88
@ -27,13 +27,10 @@ Qt containers and various Qt classes use implicit sharing.
|
||||
|
||||
The scenario will be:
|
||||
|
||||
#. renderer job (doing preparation in the GUI thread) calls
|
||||
:py:func:`QgsMapLayer.createMapRenderer()` and gets instance of this class.
|
||||
The instance is initialized at that point and should not need
|
||||
additional calls to :py:class:`QgsVectorLayer`.
|
||||
#. renderer job (still in GUI thread) stores the renderer for later use.
|
||||
#. renderer job (in worker thread) calls :py:func:`QgsMapLayerRenderer.render()`
|
||||
#. renderer job (again in GUI thread) will check :py:func:`~errors` and report them
|
||||
1. renderer job (doing preparation in the GUI thread) calls :py:func:`QgsMapLayer.createMapRenderer()` and gets instance of this class. The instance is initialized at that point and should not need additional calls to :py:class:`QgsVectorLayer`.
|
||||
2. renderer job (still in GUI thread) stores the renderer for later use.
|
||||
3. renderer job (in worker thread) calls :py:func:`QgsMapLayerRenderer.render()`
|
||||
4. renderer job (again in GUI thread) will check :py:func:`~errors` and report them
|
||||
|
||||
.. versionadded:: 2.4
|
||||
%End
|
||||
|
||||
@ -41,13 +41,10 @@ class QgsRenderedItemDetails;
|
||||
*
|
||||
* The scenario will be:
|
||||
*
|
||||
* #. renderer job (doing preparation in the GUI thread) calls
|
||||
* QgsMapLayer::createMapRenderer() and gets instance of this class.
|
||||
* The instance is initialized at that point and should not need
|
||||
* additional calls to QgsVectorLayer.
|
||||
* #. renderer job (still in GUI thread) stores the renderer for later use.
|
||||
* #. renderer job (in worker thread) calls QgsMapLayerRenderer::render()
|
||||
* #. renderer job (again in GUI thread) will check errors() and report them
|
||||
* 1. renderer job (doing preparation in the GUI thread) calls QgsMapLayer::createMapRenderer() and gets instance of this class. The instance is initialized at that point and should not need additional calls to QgsVectorLayer.
|
||||
* 2. renderer job (still in GUI thread) stores the renderer for later use.
|
||||
* 3. renderer job (in worker thread) calls QgsMapLayerRenderer::render()
|
||||
* 4. renderer job (again in GUI thread) will check errors() and report them
|
||||
*
|
||||
* \since QGIS 2.4
|
||||
*/
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user