Pad not connected if zone doesn't cover center, even if pad extends zone

[Simon Richter]

When two zones with different priority intersect, pads that are connected to the lower prioritized zone's net still push the higher priority zone away (good), but the lower priority zone is not extended technically, so it is possible to make the pad appear unconnected.

See the attachment for an example -- the "GREEN-" zone pushes away the "+5V" zone, but the "+5V" pad still wins, giving the zone a useful shape. It would be great if the "+5V" zone would be properly extended over the pad, so the connection is registered correctly.

[Novak Tamas (novak-7)]

Confirmed in BZR6709.
If a filled zone touches a pad what belongs to the net of that zone, pad is considered connected.
If pad's center is covered by zone, ratsnest line disappears --as pad is connected.
If zone doesn't cover pad's center, but touches a part of the pad, ratsnest line looks like pad was NOT connected, but Design Rule Check still doesn't list pad as unconnected.

[Seth Hillbrand (sethh)]

This was fixed by reciprocal zone-pad connectivity work