DRC reports unconnected pads errors while pads overlap in component and come from a single footprint

[Nathael Pajani]

When running DRC on a board with a PCB antenna made using a footprint with overlapping SMD copper pads, it reports unconnected pads for the pads used to create the PCB antenna even if the pads overlap by 0.25mm² of copper.

http://www.nathael.net/Data/KiCad/Conn_bug/
http://www.nathael.net/Data/KiCad/Conn_bug/Error_no_more_connections-01.png
http://www.nathael.net/Data/KiCad/Conn_bug/Error_no_more_connections-02.png

This should at most generate warnings, not unconnected pads errors, as placing nets between each pad is tricky due to the "center snapping" functionnality, and those would not move with the footprint (unless you use a selection and move both the module and the tracks, but this would also move any other selected tracks, which is definitely not what the user wants).

http://www.nathael.net/Data/KiCad/Conn_bug/Example_Use/ holds a full project with the bug.

Maybe all pads with the same name in a footprint should be considered as connected ? (I think about metal casing and such things). Do not know if this is safe though (not placing the component on the board may then lead to unconnected signals).

Thanks.

Application: kicad
Version: 4.0.0~rc1a-stable release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.3.1,wx containers,compatible with 2.8)
Platform: Linux 4.4.0-rc4-nath-64+ x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.58.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=OFF
         KICAD_SCRIPTING_MODULES=OFF
         KICAD_SCRIPTING_WXPYTHON=OFF
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=OFF