Eeschema error when using drag (G) shortcut on a component

Bug #1791839 reported by Sebastian Haas
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
Fix Released
High
Wayne Stambaugh

Bug Description

The error (MsgBox)in eeschema says the following:

Warning
HandleBlockPLace(): m_mouseCaptureCallback
= NULL

with only on button to press (OK)

This happens everytime I am trying to drag a capacitor, or a resistor (I did not test other components) by clicking the component with my left mouse (trackpad), followed by the shortcut (G) and immediately after that I press left mouse again to place it somewhere. Then the message box appers with the text above. (Using the drag option from right-click menu works fine)

After closing the message box, sometimes I can no longer select any component. I still can safe the schematic but habve to close eeschema before it works again.

If the resistor is connected with another component by a wire. The wire disappears after pressing the the drag shortcut (G).

The KiCad was installed completely fresh on a Macbook Air running on MacOS 10.13.6.

Information form KiCad:

Application: kicad
Version: (5.0.0-3-g5ebb6b6), 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 (UTF-8,STL containers,compatible with 2.8)
    Boost: 1.67.0
    OpenCASCADE Community Edition: 6.9.1
    Curl: 7.51.0
    Compiler: Clang 8.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_WXPYTHON=ON
    KICAD_SCRIPTING_ACTION_MENU=OFF
    BUILD_GITHUB_PLUGIN=ON
    KICAD_USE_OCE=ON
    KICAD_USE_OCC=OFF
    KICAD_SPICE=ON

Revision history for this message
Sebastian Haas (m0ku) wrote :
Seth Hillbrand (sethh)
Changed in kicad:
importance: Undecided → High
status: New → Triaged
milestone: none → 5.0.1
Revision history for this message
Jeff Young (jeyjey) wrote :

Appears to be a timing issue of some sort. I managed to reproduce it once, but it's quite difficult to trigger.

Revision history for this message
Wayne Stambaugh (stambaughw) wrote :

I think an acceptable fix would be to just add an assertion and return if no mouse capture callback is set. That's really what should have been done in the first place as it should not occur and is merely a warning for developers. User should never see this in release builds. I will make it so if there are no objections.

Changed in kicad:
assignee: nobody → Wayne Stambaugh (stambaughw)
Revision history for this message
KiCad Janitor (kicad-janitor) wrote :

Fixed in revision 3f7e5d2ce4d0149e154e2f89e64b3b968d2abb10
https://git.launchpad.net/kicad/patch/?id=3f7e5d2ce4d0149e154e2f89e64b3b968d2abb10

Changed in kicad:
status: Triaged → Fix Committed
Changed in kicad:
status: Fix Committed → 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.