search

buixuanan / fritzing

Automatically exported from code.google.com/p/fritzing
0 stars 0 forks source link

automatic check to make sure elements on copper layer aren't too close (DRC) #1069

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
add a "design rules check" item to the trace menu.  For each item on the 
copper layer (trace, connector, nonconnector) blow it up by the distance (10 
mil) and see if it intersects anything else in the copper layer.  Tell the 
user if so.

How easy will it be to expand the parts--will changing the svg work or does 
qt only check the bounds?

How to tell the user?  Simply highlight the offending parts?

Original issue reported on code.google.com by irasc...@gmail.com on 3 May 2010 at 3:52

GoogleCodeExporter commented 9 years ago 
r4169.  Qt only checks the bounds of SVGs, so using the rasterizer trick again. 
Keeping 
this issue open as there are still some glitches

Original comment by irasc...@gmail.com on 5 May 2010 at 11:32

GoogleCodeExporter commented 9 years ago 
mostly seems to be working, even on two sides, but when an overlap is found, 
too many parts are selected. Also, or possibly the same problem, I have seen at 
least one instance in which the selection rect is included in the overlap 
testing

Original comment by irasc...@gmail.com on 10 Jun 2010 at 10:34

GoogleCodeExporter commented 9 years ago 
check that traces and pins aren't outside the board, or even too close to the 
edge

Original comment by irasc...@gmail.com on 14 Jun 2010 at 5:56

GoogleCodeExporter commented 9 years ago 
comment 2 seems cleared up.

Original comment by irasc...@gmail.com on 2 Jul 2010 at 1:31

GoogleCodeExporter commented 9 years ago 
From Brendan:  Nice would be some kind of clickable list (dock widget?) so I 
could highlight the individual failure points.

Original comment by irasc...@gmail.com on 21 Jul 2010 at 12:07

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 21 Jul 2010 at 12:07

GoogleCodeExporter commented 9 years ago 
Finally a use for the console window? (that I finally recently removed from the 
project). But I could imagine a text-window/dock for the results which would 
either say "no overlaps found" or it could say "Part A overlaps part B", and if 
you clicked that line those two parts would be selected.  In some cases it 
could even say "Connector Q on Part A overlaps part B", and it might be 
possible to always use this formulation if this is the case.  However, being 
able to say "Connector Q on part A overlaps connector R on part B" would 
require some extra work.

Original comment by irasc...@gmail.com on 22 Jul 2010 at 9:40

GoogleCodeExporter commented 9 years ago 
DRC could be speeded up--once two parts are known to overlap, there's no need 
to further include them in the checking.  But that might miss the case when a 
part overlaps with multiple other parts.

Original comment by irasc...@gmail.com on 22 Jul 2010 at 9:43

GoogleCodeExporter commented 9 years ago 
While the DRC definitely needs a better UI, I don't think the console window is 
a good choice. The visual highlight is much stronger.
I guess the difficult question for the visual highlight is how to make it 
persistent without getting in the way. Does it disappear once the user has 
interacted with the layout again? Or can we make it stay until the problems are 
fixed?

Original comment by andre.knoerig@gmail.com on 26 Jul 2010 at 6:55

GoogleCodeExporter commented 9 years ago 
The problem is that the simultaneous visualization of each individual overlap 
needs to be clear, and this would take a whole lot of work.  So it's much 
easier if there's a text-based list of overlaps, so you can click on each 
individual one in the list, and see the relevant pair of parts selected (and 
maybe the connectors highlighted).

In other words, in order to make this happen in a reasonable time-frame, you 
have to go with a list-based approach.

Original comment by irasc...@gmail.com on 26 Jul 2010 at 8:37

GoogleCodeExporter commented 9 years ago 
Yeah, I know - let's have a little brainstorming when we get the chance. :)

Original comment by andre.knoerig@gmail.com on 26 Jul 2010 at 8:40

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 29 Sep 2010 at 6:31

GoogleCodeExporter commented 9 years ago 
1. if the drc finds nothing, put up a message box saying "no overlaps found"

2. otherwise, put up a dialog, and for each pair of overlaps found, describe 
the overlap: connector blah of part blah overlaps with tracewire blah.  Allow 
the text to be copied, and the dialog to be moved.

3. for extra credit, highlight individual connectors and/or select parts that 
are overlapping.  The only difficulty here is that this is a modal state: when 
do you turn the highlighting off.  Maybe when the dialog is closed?

4. for super extra credit, highlight the actual overlaps, maybe using a giant 
svg in its own layer?  Again, there's the modal problem: when to get rid of the 
highlighting

Original comment by irasc...@gmail.com on 5 Oct 2010 at 8:27

GoogleCodeExporter commented 9 years ago 
Issue 1271 has been merged into this issue.

Original comment by brendan....@gmail.com on 15 Oct 2010 at 1:11

GoogleCodeExporter commented 9 years ago 
I think the wiki entry for "conflict resolution" tries to address this issue as 
well (GUI wise)
http://wiki.ixds.de/Projects/Fritzing/Design_Specs/PCB_View/Conflict_resolution

Original comment by johannes...@googlemail.com on 12 Nov 2010 at 3:10

GoogleCodeExporter commented 9 years ago 
Use the new autorouter for the DRC, it's so much nicer and I assume it can 
highlight the exact areas that are overlapping?

Also, if it's faster than the old one, it might make sense to run it 
automatically on every export to production formats.

Original comment by andre.knoerig@gmail.com on 26 Jan 2011 at 9:16

GoogleCodeExporter commented 9 years ago 
Swapping out the old drc is already under way.  It is much faster than the old 
one, so it could be added to exporting as suggested.

Original comment by irasc...@gmail.com on 26 Jan 2011 at 12:23

GoogleCodeExporter commented 9 years ago 
old drc is swapped out. silkscreen overlap not yet implemented.

Original comment by irasc...@gmail.com on 27 Jan 2011 at 6:23

GoogleCodeExporter commented 9 years ago

Original comment by irasc...@gmail.com on 27 Jan 2011 at 6:25