unconnected pads when routing trace through pad

[TPepler]

e.g. it is required to connect pad (3) to (2), and to (1). If the trace is started on (3), routed through (2), and ends on (1) (by double clicking); then rats nest still shows (3) and (2) are not connected (as well as "Unconnected" list in DRC tool). However, if 2 separate routes from (3) to (2) and then (2) to (1) are used, pads are shown as connected. I suppose this could be considered a "feature", but it would be nice to have the option to allow route-throughs.

Problem occurs in pcbnew.

KiCad version info:

Application: kicad
Version: 4.0.6 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1010,GCC 6.3.0,wx containers,compatible with 2.8)
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0 nghttp2/1.19.0 librtmp/2.3
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

[Jeff Young (jeyjey)]

Related to https://bugs.launchpad.net/kicad/+bug/1718831.

[Seth Hillbrand (sethh)]

This was addressed in v5