Skip to content

Commit 499f2a8

Browse files
committed
Fix build
I'm not 100% sure if the point == mSnapMatch.point() comparison was intended be done using QgsPointXY or QgsPoint objects here! Use QgsPointXY to keep the behavior the same from before the duplicate QgsPointXY == operator was removed...
1 parent 7b1b51a commit 499f2a8

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

src/gui/qgsadvanceddigitizingdockwidget.cpp

+3-1
Original file line numberDiff line numberDiff line change
@@ -1391,7 +1391,9 @@ bool QgsAdvancedDigitizingDockWidget::applyConstraints( QgsMapMouseEvent *e )
13911391
mSnapMatch = context.snappingUtils->snapToMap( point, nullptr, true );
13921392
if ( mSnapMatch.layer() )
13931393
{
1394-
if ( ( ( mSnapMatch.hasVertex() || mSnapMatch.hasLineEndpoint() ) && ( point == mSnapMatch.point() ) )
1394+
// note ND: I'm not 100% sure if the point == mSnapMatch.point() comparison was intended be done using QgsPointXY or QgsPoint objects here!
1395+
// I'm using QgsPointXY here to keep the behavior the same from before a duplicate QgsPointXY == operator was removed...
1396+
if ( ( ( mSnapMatch.hasVertex() || mSnapMatch.hasLineEndpoint() ) && ( QgsPointXY( point ) == mSnapMatch.point() ) )
13951397
|| ( mSnapMatch.hasEdge() && QgsProject::instance()->topologicalEditing() ) )
13961398
{
13971399
e->snapPoint();

0 commit comments

Comments
 (0)