kicad-developers team mailing list archive

[Wayne Stambaugh <stambaughw@xxxxxxxxx>]

Hey Jeff,

This should "work" as long as we are opertating under the assumption
that copper overlap from different nets within a footprint is what the
footprint designer intended.  I know this may not always be the case but
until we add support for this in our board file, it might be the best
solution until we start on v6.

Cheers,

Wayne

On 10/23/2018 9:53 AM, Jeff Young wrote:
> Hi Seth and Wayne,
> 
> I had considered and discarded having DRC ignore copper graphics in
> footprints.  But the “same footprint” test didn’t occur to me, and I
> think it's just enough to make it work.
> 
> Cheers,
> Jeff.
> 
> 
>> On 23 Oct 2018, at 14:38, Wayne Stambaugh <stambaughw@xxxxxxxxx
>> <mailto:stambaughw@xxxxxxxxx>> wrote:
>>
>> On 10/23/2018 9:05 AM, Seth Hillbrand wrote:
>>> Am 2018-10-23 08:10, schrieb Jeff Young:
>>>> So I broke our net-ties work-around when I added DRC for copper
>>>> graphic items.
>>>>
>>>> I plan to add a IS_NET_TIE flag to graphic items to fix it.  (This
>>>> appears compatible with the net tie discussions of yore on the email
>>>> list.)  There will be a checkbox in Graphic Item Properties to set it.
>>>>
>>>> Question: add checkbox only to graphic items in a footprint, or to all?
>>>>
>>>> Any other issues you see?
>>>>
>>>> Thanks,
>>>> Jeff.
>>>>
>>>> Note: we save the STATUS_FLAGS as an integer in the file, so while
>>>> this constitutes a file-format change of sorts (an additional bit
>>>> might be set), it’s fully backwards-compatible.
>>>
>>> Hi Jeff-
>>>
>>> What about just avoiding DRC between footprint graphic items and the
>>> other items in the same footprint?  That would avoid the file format
>>> change while keeping the purpose of the DRC (mostly).
>>
>> I like this solution better than using the status bits for something
>> that really should be change in the footprint file format.  The status
>> bits were really mean to be transient when editing objects.  I regret
>> actually saving them in the new board file format.  It was a relic left
>> over from the legacy board file format.  Hind sight is always 20/20.
>>
>>>
>>> Best-
>>> Seth
>>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~kicad-developers
>> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
>> <mailto:kicad-developers@xxxxxxxxxxxxxxxxxxx>
>> Unsubscribe : https://launchpad.net/~kicad-developers
>> More help   : https://help.launchpad.net/ListHelp
>