Problem getting correct item active when going from eeschema to pcbnew

Bug #1848531 reported by Andrzej Pyszniak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
Unknown

Bug Description

Application: Eeschema
Version: (5.1.4-0), release build
Libraries:
    wxWidgets 3.0.4
    libcurl/7.54.0 LibreSSL/2.0.20 zlib/1.2.11 nghttp2/1.24.0
Platform: Mac OS X (Darwin 17.7.0 x86_64), 64 bit, Little endian, wxMac
Build Info:
    wxWidgets: 3.0.4 (wchar_t,STL containers,compatible with 2.8)
    Boost: 1.69.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.54.0
    Compiler: Clang 9.0.0 with C++ ABI 1002

Build settings:
    USE_WX_GRAPHICS_CONTEXT=ON
    USE_WX_OVERLAY=ON
    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

I do initial footprint placement having eeschema opened on one desktop, pcbnew on another, then selecting a symbol in eeschema and swiping to go to the other desktop where the corresponding footprint is already highlighted in pcbnew and I can just hit 'm' to move it do a desired place.

HOWEVER, this often doesn't work right off the bat. Sometimes I just hear a dull 'bong' system sound, like I'd try to use some inactive option. A way to deal with that is to pan the view slightly (swiping two fingers on the touchpad). After that, the 'm' is properly recognized and acted upon (also, sometimes hitting 'm' multiple times unlocks it. But only sometimes).

In this whole situation, the window focus itself gets properly changed from eeschema to pcbnew, which I see because "Route" menu appears in the system menu bar. Also, the desired footprint is already highlighted. Yet, 'm' command (as well as others) is not recognized.

Tags: macos ui
Revision history for this message
Michael Kavanagh (michaelkavanagh) wrote :

This sounds like a window focus issue which is handled by macOS (in this case). I'm not sure there is anything we can do about this.

@Devs, any other views on how to proceed?

Changed in kicad:
status: New → Incomplete
tags: added: macos ui
Revision history for this message
Andrzej Pyszniak (newmanx) wrote :

But the window seems to be focused fine. Meanwhile I read some bug reports mentioning unresponsive keyboard shortcuts. Maybe it's this kind of a problem.

Revision history for this message
Andrzej Pyszniak (newmanx) wrote :

But then, I checked it on my Linux machine and after a couple dozen tries I haven't got the problem. So I guess you're right.

Revision history for this message
Jeff Young (jeyjey) wrote :

I dug into this during 5.0 development, but without success. It's a minefield, if I recall correctly.

Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

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

Changed in kicad:
status: Incomplete → Expired
Changed in kicad:
importance: Undecided → Unknown
status: Expired → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.