Cannot select DRC Markers if F.Cu layer is invisible

[Drew Jaworski]

I have not experimented with different combinations DRC errors and markers, but specifically I have "ErrType(5): track near via" DRC Markers (regarding a pad and track on F.Cu) that cannot be selected when I have the F.Cu layer set to invisible (via the checkbox in the Layers Manager).

I am not actually sure if this is a bug or a feature; but I like to remove the visual clutter of the tracks when looking for DRC Markers, select the Marker, then make the layer visible if needed. It was annoying trying to figure out why I could not select the DRC Marker, until I realized setting the layer to visible allowed me to select it.

Application: kicad
Version: (5.0.2)-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 8 (build 9200), 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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=ON
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

[Drew Jaworski (jaworskidrew)]

After more testing, it looks like this is a bug - I have a DRC Marker "ErrType(16) - Two track ends too close" for two tracks on B.CU; I cannot select the DRC Marker unless F.Cu is visible!

[Drew Jaworski (jaworskidrew)]

Possibly related to bug #1793357

[Drew Jaworski (jaworskidrew)]

Also can't select DRC Markers, in any layer visibility case, if high contrast mode is on...

[Seth Hillbrand (sethh)]

Would you be able to test a nightly build to see if you have this issue there?

It looks like the bug fix might only exist in the master branch.

[Drew Jaworski (jaworskidrew)]

Yes, it is still an issue in the latest nightly build.

However, the related issue I brought up in #3 is fixed in the latest nightly build.

Application: kicad
Version: (6.0.0-rc1-dev-1376-g9490fd9d3), 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 8 (build 9200), 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)]

Fixed in revision 5f4530493af8c7a87ec0ccefd4c24847fc5c9935
https://git.launchpad.net/kicad/patch/?id=5f4530493af8c7a87ec0ccefd4c24847fc5c9935