After placement, various eeschema features no longer work

Bug #1825169 reported by Ron Burkey
This bug report is a duplicate of:  Bug #1825192: Open Choose symbol continually. Edit Remove
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
KiCad
New
Undecided
Unassigned

Bug Description

Placing text or a symbol on a schematic breaks a lot of eeschema features which as far as I know work fine prior to placing the text or symbol. The only workaround is to exit and reenter eeschema after you do that. Placing wires still seems to work fine. There's so much weird stuff randomly broken, I can even describe it properly here. I've made a video that runs through various things I've discovered, ineptly I'm afraid, since I have no mic and had to just type my commentary directly in the video. (Sorry!)

I believe there's probably a lot of other stuff similar to what's in the video that's broken, but this rev (the current nightly) has become essentially unusable for me, so I've had to move on to other things for today rather than continue trying to coax it to work.

Here's a video link: https://drive.google.com/open?id=15UqwiXn4BQdLzWk-YHgXJJ8lZmzlUBD5

Application: kicad
Version: 5.1.0-unknown-ead5bfe~82~ubuntu16.04.1, release build
Libraries:
    wxWidgets 3.0.2
    libcurl/7.47.0 OpenSSL/1.0.2g zlib/1.2.11 libidn/1.32 librtmp/2.3
Platform: Linux 4.4.0-53-generic x86_64, 64 bit, Little endian, wxGTK
Build Info:
    wxWidgets: 3.0.2 (wchar_t,wx containers,compatible with 2.8) GTK+ 2.24
    Boost: 1.58.0
    OpenCASCADE Community Edition: 6.8.0
    Curl: 7.47.0
    Compiler: GCC 5.4.0 with C++ ABI 1009

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

Tags: eeschema
Ron Burkey (rburkey)
description: updated
Revision history for this message
Jeff Young (jeyjey) wrote :

This is due to having 1/2 of the tools moved to the modern toolset.

I've put in a shim to allow the two to get along for now. (The issue is that modern tools cancel other tools when started, but the legacy tools don't. So the modern tool gets "stuck" until you choose another modern tool.)

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.