Cursor does not return to "selection" cursor after editing value or reference of placed component

[John Hannum]

Here is the Kicad information:
Application: kicad
Version: 4.0.7 release build
wxWidgets: Version 3.0.3 (debug,wchar_t,compiler with C++ ABI 1011,GCC 7.1.0,wx containers,compatible with 2.8)
Platform: Windows 8 (build 9200), 64-bit edition, 64 bit, Little endian, wxMSW
Boost version: 1.60.0
Curl version: libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
         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

Here is the OS information:
Windows 10, 64-bit; Version 1709 (OS Build 16299.64)

Start with a fresh installation of Kicad and a new project. A new schematic is opened from the main window. Using the Place Component tool, a new component, for example a resistor, is placed. A right click on the component opens a context menu. Edit Component is selected opening a second context menu to designate what to edit. If Value or Reference is selected in this second context menu, a dialog box opens enabling the user to edit the value or reference data for the component. When the editing is completed, and the user closes the dialog box, the cursor is left in a peculiar state. It is just an arrow, with no attached cross-hairs, and won't do anything but move around the screen in response to the mouse. The only way I have found to restore the cursor to normal operation is to click in the window of another program and click back in the EESchema window. Opening the Library Browser, Library Editor, or Footprint Editor by clicking on the button in the toolbar at the top of the window, clicking in the window of the tool that opens, and then clicking back in the EESchema window also works, probably because those editors are separate programs.
If one attempts to edit the value or reference data of a component before placing it, a similar condition arises but with an additional issue. If one attempts to move the cursor up to the toolbar at the top of the screen to click on one of the library or footprint tools, the component follows the cursor. In fact, the component will follow the cursor all around the screen, but it cannot be placed. Furthermore, the cursor seems to be trapped in the EESchema window.

[Charley Carter (cnc1)]

I am having this same issue on:

KiCad Version 4.0.7, release build
Windows 10 Pro (64-bit)
Version 1709
OS Build 16299.64

It was working when I first installed it. I believe it started when Windows 10 updated to the Fall Creators Update.

It also happens with PcbNew. It effectively makes the program unusable. I tried the Nov. 25th, nightly build and it had the same problem.

[Charley Carter (cnc1)]

These three bug reports (1654854, 1734797, 1734882) all seem to be similar.

[Charley Carter (cnc1)]

As a workaround, the problem only seems to occur when using right-click and selecting edit in the context menu. Hover over the component and use the "e" shortcut key and the cursor doesn't freeze. Likewise for edit value (v), footprint (f), etc.

[Jeff Young (jeyjey)]

@Chris, didn't you fix something similar to this recently?

[Wayne Stambaugh (stambaughw)]

I think the fix you are talking about is for the opposite problem where the cursor would snap back to the point the context menu was opened even when it was dismissed by clicking outside the context menu.

[Jeff Young (jeyjey)]

He he... no, that fix was mine. But God only knows what was ringing a bell in my somewhat-challenged memory. ;)

[Wayne Stambaugh (stambaughw)]

LOL! Sorry about that. Obviously I can relate relate to the challenged
memory issue.

On 2/7/2018 2:18 PM, Jeff Young wrote:
> He he... no, that fix was mine. But God only knows what was ringing a
> bell in my somewhat-challenged memory. ;)
>

[Jeff Young (jeyjey)]

This bug fix: https://bugs.launchpad.net/kicad/+bug/1746507 may have impact here.

@Charley, could you see if it still happens for you using one of the recent nightly builds?

[Launchpad Janitor (janitor)]

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