Skip to content

Commit 073c5be

Browse files
committedNov 23, 2018
Remove progress task from identify action
Seems that some providers trigger an issue with the progress task (likely due to a local event loop running on the main thread triggering a processEvents call). Workaround the issue by just removing the progress task -- it's unlikely to be missed anyway. Fixes #20459 (cherry picked from commit 57c117c)
1 parent 8ce3e8b commit 073c5be

File tree

1 file changed

+0
-10
lines changed

1 file changed

+0
-10
lines changed
 

‎src/app/qgsmaptoolidentifyaction.cpp

Lines changed: 0 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,6 @@
3838
#include "qgsunittypes.h"
3939
#include "qgsstatusbar.h"
4040
#include "qgsactionscoperegistry.h"
41-
#include "qgsproxyprogresstask.h"
4241
#include "qgssettings.h"
4342
#include "qgsmapmouseevent.h"
4443

@@ -112,14 +111,6 @@ void QgsMapToolIdentifyAction::showAttributeTable( QgsMapLayer *layer, const QLi
112111
void QgsMapToolIdentifyAction::identifyFromGeometry()
113112
{
114113
resultsDialog()->clear();
115-
116-
QgsProxyProgressTask *task = new QgsProxyProgressTask( tr( "Identifying features" ) );
117-
QgsApplication::taskManager()->addTask( task );
118-
119-
connect( this, &QgsMapToolIdentifyAction::identifyProgress, task, [ = ]( int i, int n )
120-
{
121-
task->setProxyProgress( static_cast<double>( i ) * 100.0 / n );
122-
} );
123114
connect( this, &QgsMapToolIdentifyAction::identifyMessage, QgisApp::instance(), &QgisApp::showStatusMessage );
124115

125116
QgsGeometry geometry = mSelectionHandler->selectedGeometry();
@@ -139,7 +130,6 @@ void QgsMapToolIdentifyAction::identifyFromGeometry()
139130

140131
QList<IdentifyResult> results = QgsMapToolIdentify::identify( geometry, mode, AllLayers );
141132

142-
task->finalize( true );
143133
disconnect( this, &QgsMapToolIdentifyAction::identifyMessage, QgisApp::instance(), &QgisApp::showStatusMessage );
144134

145135
if ( results.isEmpty() )

0 commit comments

Comments
 (0)
Please sign in to comment.