Internal nets in footprints

[negative2404]

I would be extremely useful feature to allow internal connection of pins in PCB footprint.
This would help in designing boards with devices that have internal pads connected (e.g. pusbuttons).
This would automatically solve feature request #2011581 as bridge would be a 0805/1205 footprint with internally connected pads.
Other solution would be to make the internal nets available in EESCHEMA components.
I don't know which is better or easier to implement but each have both advantages and disadvantages.
For example:
- PCB footptints shall be independent on chip type (e.g. DIP) so it would be better to have this in EESCHEMA
- EECHEMA components builds a schematic so pusbutton just connects 2 pins, but the PCB footprint consists usually of 2 pairs of connected pins so routing woule be easier if PCBNEW knows that these pins are connected.
- interconnection of pins in PCB footprints would be extremely nice because for adding a bridge, one could add a '1206 bridge' footprint and connect pins to a single net and PCB verification tool would report no error.

If both of the ideas are implemente, there would be automatically new feature: macro circuits. One could make a set of commonly used circuits and its footprints which would speedup board design.

It would be very kind of you if you consider the feature I have described.

Kind regards.

[nobody (nobody-users)]

Quick potential solution for internal nets in PCB layout could be assigning a kind of 'local net names' in each pin. e.g. assign pin1 and pin2 net name like $local_interconn would affect a connection of pin1 and 2.
I do not know whether the same solution is possible in EESCHEMA, but I think it is.

[xzcvczx (xzcvczx)]

Having 2 pads with the same numbers will have pcbnew airwire between them, so this is already fixed, The bridge has a seperate bug report