pcbnew -> eeschema cross-probe does not indicate component/pin

Bug #1796990 reported by Seth Hillbrand on 2018-10-09
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Low
Tomasz Wlostowski

Bug Description

When clicking on a component in pcbnew, the cross-probe to eeschema centers the component but doesn't indicate which component it is. Previously, the indicator was a small cursor "+" over the component but could be anything. Just needs to be enough to pick the correct component out of the group.

Application: kicad
Version: (6.0.0-rc1-dev-848-g13997f005), debug build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.52.1 OpenSSL/1.0.2l zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Platform: Linux 4.9.0-8-amd64 x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.62.0
    Curl: 7.52.1
    Compiler: GCC 6.3.0 with C++ ABI 1010

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

Changed in kicad:
milestone: none → 5.1.0
tags: added: eeschema gal
Maciej Suminski (orsonmmz) wrote :

Just a note: cross-probing does point to a pin/component, but the crosshair needs to be enabled in eeschema to see that.

Changed in kicad:
importance: Undecided → Critical
importance: Critical → Low
Tomasz Wlostowski (twlostow) wrote :

How about highlighting the component (in conjunction with moving the crosshair)?

Tom

Changed in kicad:
assignee: nobody → Tomasz Wlostowski (twlostow)
Changed in kicad:
status: New → Fix Committed
Changed in kicad:
status: Fix Committed → Fix Released
MightyPork (mighty-pork) wrote :

This worked in 5.0, but stopped working in 5.1 and is still broken in 5.1.0-373-ge808c7f95. Centering works, but in 5.0 the item turned red when cross-probed, which was really useful. Now it isn't highlighted and you have to enable "show crosshairs always" to see anything.

@mighty-pork, if you believe this behaviour is broken/there is a regression, please open a new bug report.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers