Bug 1031406

Summary: pcbnew: flood fill connects to other nets
Product: [Fedora] Fedora Reporter: Gerd v. Egidy <gerd>
Component: kicadAssignee: Alain Portal <alain.portal>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 19CC: alain.portal, chitlesh, thibault.north
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-20 23:45:44 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
simple example file to make reproducing more easy
none
screenshot showing the problem (made with version 2013-06-11)
none
screenshot without the problem (made with version 2013-07-07)
none
Works for me with 2013-06-11 none

Description Gerd v. Egidy 2013-11-17 17:19:20 UTC
Created attachment 825209 [details]
simple example file to make reproducing more easy

Description of problem:

when doing a flood fill in pcbnew, the fill connects traces of other nets. There is no isolation space kept between the different nets.


Version-Release number of selected component (if applicable):
kicad-2013.06.11-1.rev4021.fc19

How reproducible:
always

Steps to Reproduce:
1. create a simple schema with at least 2 different nets
2. create a layout for this schema
3. draw traces for each net
4. add a fill area to the full pcb, connect it to one of the nets
5. fill the fill area

I'll attach a pcbnew-file to make reproducing more easy.

Actual results:
both nets are connected to the fill area, there is no isolation to the trace of the other net.
See attached screenshot fill-error-2013-06-11.png

Expected results:
isolation space added between fill area and other trace
See attached screenshot fill-ok-2013-07-07.png

Additional info:
This seems to be fixed with upstream release 2013-07-07. So it would probably be more easy to just switch to that release than to isolate and backport just the fix for this bug.

Comment 1 Gerd v. Egidy 2013-11-17 17:20:31 UTC
Created attachment 825210 [details]
screenshot showing the problem (made with version 2013-06-11)

Comment 2 Gerd v. Egidy 2013-11-17 17:21:31 UTC
Created attachment 825211 [details]
screenshot without the problem (made with version 2013-07-07)

Comment 3 Alain Portal 2013-11-20 16:00:53 UTC
Created attachment 826728 [details]
Works for me with 2013-06-11

I intensely use 2013-06-11-rev4021 on EL6, with zone fill and zone exclusion, I never get a such problem...
And I can't reproduce the bug with your board...

Comment 4 Gerd v. Egidy 2013-11-20 16:55:22 UTC
Thank you for testing this.

Do you know if some setting could cause such behavior?

I will try this again on a fresh vm and try to narrow it down.

Comment 5 Gerd v. Egidy 2013-11-20 23:45:44 UTC
ok, did some testing. Seems like I messed up some libraries, it is working with the stock install and my configuration.

Sorry for the noise.