Skip to content

Commit a6650e4

Browse files
committedNov 15, 2014
Add note about QgsMapCanvas::refresh() behavior
1 parent d91694a commit a6650e4

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed
 

‎doc/api_break.dox

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,10 @@ This page tries to maintain a list with incompatible changes that happened in pr
2121
\subsection qgis_api_break_mtr Multi-threaded Rendering
2222

2323
<ul>
24+
<li>QgsMapCanvas::refresh() only schedules a map refresh (in near feature) and returns immediately - before it would do the drawing immediately
25+
and return when the map is redrawn. A call to refresh() will have no effect if there is already a scheduled pending refresh.
26+
When map canvas does actual rendering, it will first emit renderStarting() signal, once done it will emit mapCanvasRefreshed().
27+
The client code doing refresh() in order to later save map image should be updated to use new QgsMapRendererJob API which is better suited for such task.
2428
<li>QgsPluginLayer::draw() is now run in a background thread. It is recommended to implement newly added QgsPluginLayer::createMapRenderer()
2529
method instead of using QgsPluginLayer::draw().
2630
</ul>

0 commit comments

Comments
 (0)
Please sign in to comment.