Footprint Editor - Some shortcuts (e.g. "M" used to move) don't work

Bug #1655617 reported by Silviu Laurentiu
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
KiCad
Expired
Medium
Unassigned

Bug Description

     Reproduce the issue:
     Open the project (I attached my project) -> open Pcbnew -> Right click on a footprint -> Footprint ... on F.Cu -> Edit with Footprint Editor -> Try to move a text or a pad, using "M" keyboard. For me, the moving using "M" don't work.
     If the Pcbnew window is selected and click on left mouse button somewhere, and then go again to Footprint Editor window, "M" shortcut start to work again.
     Another solution to start working "M", is to open any kind of window from Footprint Editor menu. E.g. open "File" -> "Set Active Library" window.

Application: kicad
Version: 4.0.5-e0-6337~49~ubuntu16.04.1 release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.4.0,wx containers,compatible with 2.8)
Platform: Linux 4.4.0-21-generic x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.58.0
         USE_WX_GRAPHICS_CONTEXT=OFF
         USE_WX_OVERLAY=OFF
         KICAD_SCRIPTING=ON
         KICAD_SCRIPTING_MODULES=ON
         KICAD_SCRIPTING_WXPYTHON=ON
         USE_FP_LIB_TABLE=HARD_CODED_ON
         BUILD_GITHUB_PLUGIN=ON

Revision history for this message
Silviu Laurentiu (silviulaurentiu) wrote :
Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

I can confirm this. Additionally, the bug is still present in the master branch, and switching active layers also makes the hotkeys work again.

Changed in kicad:
status: New → Confirmed
importance: Undecided → Medium
tags: added: legacy modedit pcbnew
Revision history for this message
Maciej Suminski (orsonmmz) wrote :

I cannot reproduce the problem here. Do you use an exotic window manager?

Revision history for this message
Silviu Laurentiu (silviulaurentiu) wrote : Re: [Bug 1655617] Re: Footprint Editor - Some shortcuts (e.g. "M" used to move) don't work

The issue occurs when Kicad run on Linux Mint 18.0, 64 bit, . On Windows 7,
64 bit, this not occur.

On Thu, Jan 19, 2017 at 10:21 AM, Maciej Sumiński <
<email address hidden>> wrote:

> I cannot reproduce the problem here. Do you use an exotic window
> manager?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1655617
>
> Title:
> Footprint Editor - Some shortcuts (e.g. "M" used to move) don't work
>
> Status in KiCad:
> Confirmed
>
> Bug description:
> Reproduce the issue:
> Open the project (I attached my project) -> open Pcbnew -> Right
> click on a footprint -> Footprint ... on F.Cu -> Edit with Footprint Editor
> -> Try to move a text or a pad, using "M" keyboard. For me, the moving
> using "M" don't work.
> If the Pcbnew window is selected and click on left mouse button
> somewhere, and then go again to Footprint Editor window, "M" shortcut start
> to work again.
> Another solution to start working "M", is to open any kind of
> window from Footprint Editor menu. E.g. open "File" -> "Set Active Library"
> window.
>
>
> Application: kicad
> Version: 4.0.5-e0-6337~49~ubuntu16.04.1 release build
> wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC
> 5.4.0,wx containers,compatible with 2.8)
> Platform: Linux 4.4.0-21-generic x86_64, 64 bit, Little endian, wxGTK
> Boost version: 1.58.0
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> USE_FP_LIB_TABLE=HARD_CODED_ON
> BUILD_GITHUB_PLUGIN=ON
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1655617/+subscriptions
>

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Do you know what is your window manager/desktop environment (GNOME, KDE, Xfce, something unusual)? I cannot reproduce the problem, and I tried on Linux with awesome wm and xfce.

Revision history for this message
Chris Pavlina (pavlina-chris) wrote :

I'm using i3. Can check on something different later today.

Revision history for this message
jean-pierre charras (jp-charras) wrote :

I also cannot reproduce this issue on Ubuntu 16.04 Unity.

Revision history for this message
Silviu Laurentiu (silviulaurentiu) wrote :

​I use Linux Mint 18.0 MATE​

On Thu, Jan 19, 2017 at 2:03 PM, jean-pierre charras <
<email address hidden>> wrote:

> I also cannot reproduce this issue on Ubuntu 16.04 Unity.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1655617
>
> Title:
> Footprint Editor - Some shortcuts (e.g. "M" used to move) don't work
>
> Status in KiCad:
> Confirmed
>
> Bug description:
> Reproduce the issue:
> Open the project (I attached my project) -> open Pcbnew -> Right
> click on a footprint -> Footprint ... on F.Cu -> Edit with Footprint Editor
> -> Try to move a text or a pad, using "M" keyboard. For me, the moving
> using "M" don't work.
> If the Pcbnew window is selected and click on left mouse button
> somewhere, and then go again to Footprint Editor window, "M" shortcut start
> to work again.
> Another solution to start working "M", is to open any kind of
> window from Footprint Editor menu. E.g. open "File" -> "Set Active Library"
> window.
>
>
> Application: kicad
> Version: 4.0.5-e0-6337~49~ubuntu16.04.1 release build
> wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC
> 5.4.0,wx containers,compatible with 2.8)
> Platform: Linux 4.4.0-21-generic x86_64, 64 bit, Little endian, wxGTK
> Boost version: 1.58.0
> USE_WX_GRAPHICS_CONTEXT=OFF
> USE_WX_OVERLAY=OFF
> KICAD_SCRIPTING=ON
> KICAD_SCRIPTING_MODULES=ON
> KICAD_SCRIPTING_WXPYTHON=ON
> USE_FP_LIB_TABLE=HARD_CODED_ON
> BUILD_GITHUB_PLUGIN=ON
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1655617/+subscriptions
>

Revision history for this message
Fabián Inostroza (fabianinostroza) wrote :

I'm running Debian Stretch with MATE and I also have this problem.

Revision history for this message
Maciej Suminski (orsonmmz) wrote :

Is this still the case? I have tried KiCad with Ubuntu Mate 16.04 (virtual machine) and it worked fine. If there are still problems, I will check with Linux Mint to exactly recreate the testing environment.

tags: added: fpedit
removed: modedit
Revision history for this message
Jeff Young (jeyjey) wrote :

Is this still an issue?

Changed in kicad:
status: Confirmed → Incomplete
Revision history for this message
Silviu Laurentiu (silviulaurentiu) wrote :

Yes, for me is still an issue when I run Kicad 4.0.7-e2-6376-58-ubuntu16.04.1.

Thanks a lot!

tags: added: 4.0.5 4.0.7
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for KiCad because there has been no activity for 60 days.]

Changed in kicad:
status: Incomplete → Expired
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.