Dragging a track which is violating DRC in Shove mode

[eelik]

For example changing track width of existing tracks may lead to situation where Shove routing mode doesn't let me drag a track to fix the situation, even when there's empty space in other side of the track. I have to change to Highlight collisions/allow violations mode to to that. And then I can't push other tracks away.

So, in my opinion it should be possible to drag a track to a place where it doesn't violate DRC even when it's violating when the drag begins.

(The track seems to be locked if the violation happens in any segment, not just in the segement I try to move. I think locking shouldn't happen in this situation if the segements to be moved aren't violating DRC.)

(Also there's no indication about the situation, that there's a violation which prevents moving, or where the violation is.)

[Oivind Toien (otoien)]

I run into this problem with locked tracks because of DRC violations quite frequently. This is one of the few situations where I have to switch to legacy canvas to escape from the locked situation. I am not sure how this would be solved when the legacy canvas is gone.

Application: KiCad
Version: (5.1.2-151-gc951ca6f4)-1, release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.61.1 OpenSSL/1.1.1 (WinSSL) zlib/1.2.11 brotli/1.0.6 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) nghttp2/1.34.0
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
    wxWidgets: 3.0.4 (wchar_t,wx containers,compatible with 2.8)
    Boost: 1.68.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.61.1
    Compiler: GCC 8.2.0 with C++ ABI 1013

Build settings:
    USE_WX_GRAPHICS_CONTEXT=OFF
    USE_WX_OVERLAY=OFF
    KICAD_SCRIPTING=ON
    KICAD_SCRIPTING_MODULES=ON
    KICAD_SCRIPTING_PYTHON3=OFF
    KICAD_SCRIPTING_WXPYTHON=ON
    KICAD_SCRIPTING_WXPYTHON_PHOENIX=OFF
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[KiCad Janitor (kicad-janitor)]

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/2275