Highlight component between eeschema/pcbnew (new eeschema toolset) mismatch
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KiCad |
Fix Committed
|
Low
|
Jeff Young |
Bug Description
There's small mismatch between eeschema/pcbnew component highlight with the new eeschema toolset.
1. Select a footprint. The corresponding symbol will be red.
2. Select a symbol. The corresponding footprint will be selected.
However, the previously highlighted (red) symbol is still red. So, there's a mismatch between the red marking and footprint selection.
Application: kicad
Version: (5.1.0-
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,
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_
USE_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
KICAD_
BUILD_
KICAD_
KICAD_
KICAD_SPICE=ON
Changed in kicad: | |
milestone: | none → 6.0.0-rc1 |
tags: | added: eeschema pcbnew |
Changed in kicad: | |
assignee: | nobody → Jeff Young (jeyjey) |
Changed in kicad: | |
importance: | Undecided → Low |
status: | New → Triaged |
I can't even de-red the red symbol under some circumstances. Selecting another footprint makes another symbol red, but it stays red. There's some combination of actions which triggers this and something which clears it, but I didn't find the logic yet.