See also Bug #1716702, https://bugs.launchpad.net/kicad/+bug/1716702, and also Bug #1745981, https://bugs.launchpad.net/kicad/+bug/1745981.
A similar, but not indentical, bug has occured in recent nightly builds.
Create a board with two overlapping items, for example graphic lines with overlapping end points. Use the RMB to open the context menu, clarify selection, open Properties, click OK. Now zooming with the middle mouse button is stuck to a one point.
There have been so many of similar bugs with the mouse cursor (or the point which is active for mouse actions) that it makes me wonder if there's something wrong with the code architecture. I hope these can be fixed for good.
Application: kicad
Version: (2018-01-30 revision 342197bb3)-makepkg, release build
Libraries:
wxWidgets 3.0.3
libcurl/7.54.1 OpenSSL/1.0.2l zlib/1.2.11 libssh2/1.8.0 nghttp2/1.23.1 librtmp/2.3
Platform: Windows 7 (build 7601, Service Pack 1), 64-bit edition, 64 bit, Little endian, wxMSW
Build Info:
wxWidgets: 3.0.3 (wchar_t,wx containers,compatible with 2.8)
Boost: 1.60.0
Curl: 7.54.1
Compiler: GCC 7.1.0 with C++ ABI 1011
Build settings:
USE_WX_GRAPHICS_CONTEXT=OFF
USE_WX_OVERLAY=OFF
KICAD_SCRIPTING=ON
KICAD_SCRIPTING_MODULES=ON
KICAD_SCRIPTING_WXPYTHON=ON
KICAD_SCRIPTING_ACTION_MENU=ON
BUILD_GITHUB_PLUGIN=ON
KICAD_USE_OCE=ON
KICAD_SPICE=ON
Another way to trigger a similar bug:
1. A board with a graphic line.
2. Select the line somewhere in the middle of it.
3. Go on one of the endpoints so that the cursor is snapped to it.
4. Context menu -> Properties.
5. Cancel with escape.
What do you say, are these symptoms of one bug, or are there several? Should I report more if I find them, or is it enough to have one reproducible "open context menu, do something, cursor is stuck" situation?