From 24d95b410de9114a50c7bee99414f6b9091ab68b Mon Sep 17 00:00:00 2001 From: Jon Evans Date: Thu, 11 May 2023 13:08:45 -0400 Subject: [PATCH] PNS: Don't use clearance epsilon for calculating shove distances Fixes https://gitlab.com/kicad/code/kicad/-/issues/14707 (cherry picked from commit 2e603159594efafc9d7e3b2a86cbea5792229f12) --- pcbnew/router/pns_shove.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/pcbnew/router/pns_shove.cpp b/pcbnew/router/pns_shove.cpp index 76b270cc88..6fc48db095 100644 --- a/pcbnew/router/pns_shove.cpp +++ b/pcbnew/router/pns_shove.cpp @@ -134,7 +134,7 @@ int SHOVE::getClearance( const ITEM* aA, const ITEM* aB ) const if( m_forceClearance >= 0 ) return m_forceClearance; - return m_currentNode->GetClearance( aA, aB ); + return m_currentNode->GetClearance( aA, aB, false ); } @@ -440,7 +440,7 @@ SHOVE::SHOVE_STATUS SHOVE::ShoveObstacleLine( const LINE& aCurLine, const LINE& // hull it will be at the appropriate clearance. int obstacleLineWidth = aObstacleLine.Width(); - int clearance = getClearance( &aCurLine, &aObstacleLine ) + 1; + int clearance = getClearance( &aCurLine, &aObstacleLine ); int currentLineSegmentCount = aCurLine.SegmentCount(); HULL_SET hulls;