haskal
/
kicad
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Remove silk_clearance == 0 hack now that we have implied rules. 

Fixes https://gitlab.com/kicad/code/kicad/issues/5977
This commit is contained in:
Jeff Young 2020-10-12 21:13:02 +01:00
parent 3759c71558
commit 5afae757ff
1 changed files with 4 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
pcbnew/drc/drc_test_provider_silk_clearance.cpp
View File

@ -131,24 +131,16 @@ bool DRC_TEST_PROVIDER_SILK_CLEARANCE::Run()
aRefItem->parent,
aTestItem->parent,
aLayers.second );
if( constraint.IsNull() )
return true;
int minClearance = constraint.GetValue().Min();
int actual;
VECTOR2I pos;
accountCheck( constraint );
if( minClearance == 0 )
{
// MinClearance == 0 means the author didn't specify anything and we want
// to perform a basic silk : silk collision test.
//
// aLayers.first is always a silk layer, so we just need to check that
// aLayers.second matches.
//
if( aLayers.second != aLayers.first )
return true;
}
// Graphics are often compound shapes so ignore collisions between shapes in a
// single footprint or on the board.
PCB_SHAPE* refGraphic = dynamic_cast<PCB_SHAPE*>( aRefItem->parent );