Walk around and highlight collision do not work, option reverts to PNS

[Thomas Figueroa]

Application: kicad
Version: (2017-03-19 revision 280c6dc3a)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.53.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0 nghttp2/1.19.0 librtmp/2.3
Platform: Windows 10 Pro Insider (build 15061), 64-bit edition, 64 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.63.0
Curl: 7.53.1
KiCad - Compiler: GCC 6.3.0 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  KICAD_SCRIPTING_ACTION_MENU=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON

Just as the title says. In the nightly build, the walk around and highlight collision options for interactive routing do not work. It simply reverts to the PNS router for each option.

[Tomasz Wlostowski (twlostow)]

Hi Thomas, I can't reproduce this bug... Running latest build here.

Tom

[Thomas Figueroa (tom-figueroa)]

Here are the steps I took to reproduce the error:
1. In pcbnew, set the interactive router to shove.
2. Exit KiCad entirely
3. Run pcbnew again
4. Router will be set to Walk Around, but will push and shove traces on the board.

[Rogier Lodewijks (rogier-f)]

With some newer builds I'm experiencing something similar, though not the same, still might be related.

Regardless of the interactive router mode I choose (e.g. shove, walk around or show collisions) the router "sticks" to walk around. When dragging a track, other tracks do get shoved.

I'm running Windows 10 x86-64, tried on 2 PC's with two different projects. Tested builds from 9 april, 13 april and 10 march 2017.

[Julien Faucher (suzizecat)]

Well, i found out that using the 'E' key (by default) doesn't affect interactive router anymore but using the Preferences > Interactive Routing menu just work fine.

I think that a link between the two functionalities have been broken...

I'm running on nighty on Win 10 up to date

Application: kicad
Version: (2017-05-08 revision d4e41c4f9)-makepkg, release build
Libraries: wxWidgets 3.0.2
           libcurl/7.52.1 OpenSSL/1.0.2k zlib/1.2.11 libssh2/1.8.0 nghttp2/1.19.0 librtmp/2.3
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
- Build Info -
wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
Curl: 7.52.1
KiCad - Compiler: GCC 6.3.0 with C++ ABI 1010
        Settings: USE_WX_GRAPHICS_CONTEXT=OFF
                  USE_WX_OVERLAY=OFF
                  KICAD_SCRIPTING=ON
                  KICAD_SCRIPTING_MODULES=ON
                  KICAD_SCRIPTING_WXPYTHON=ON
                  KICAD_SCRIPTING_ACTION_MENU=ON
                  BUILD_GITHUB_PLUGIN=ON
                  KICAD_USE_OCE=ON

[Launchpad Janitor (janitor)]

[Expired for KiCad because there has been no activity for 60 days.]

[Nick Østergaard (nickoe)]

@Thomas, Is this still an issue?

[Thomas Figueroa (tom-figueroa)]

Yup, it's still an issue. Julian Faucher accurately describes the problem.

[Nick Østergaard (nickoe)]

I reopened this bug because comment #7 says that this is still an issue, but that is still a long time ago. Please retest if possible.

[Thomas Figueroa (tom-figueroa)]

I can't replicate this now no matter what I try, so I'm going to go out on a limb and say it isn't an issue.

[Nick Østergaard (nickoe)]

OK, I will mark it as Invalid for now, since it does not seem to be an issue anymore and there is no specific commit that attempts to fix it.