python console wait cursor

[Mark Roszko]

1. Open pcbnew python console
2. Type in help()
3. Cursor becomes "loading" cursor.
4. Close python console
5. Loading cursor is now stuck on pcbnew window and doesnt change

The loading cursor ends up applying to all kicaad windows even eeschema if pcbnew was opened from the kicad manager. Also if you close the kicad project manager, it seg faults.

In this case Im using one of Nick OE's latest windows prebuilt binaries. bzr 6097

[firewalker (firew4lker)]

I think this is the default behavior. If you type quit to leave interactive help. The cursor returns to normal state. If you just close the window the interactive help does not terminate. On GNU/Linux even closing all the windows, kicad does not terminate.

Maybe the bug should be something like "Interactive help does not terminate upon python script window close event".

Application: kicad
Version: (2015-08-17 BZR 6098)-product release build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1009,GCC 5.2.0,wx containers,compatible with 2.8)
Platform: Linux 4.1.4-1-ARCH i686, 32 bit, Little endian, wxGTK
Boost version: 1.54.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

[Mark Roszko (mark-roszko)]

Actually having the wait cursor when trying to use interactive help is also really bad even before closing the window. You don't get the caret cursor over the console like you should.

[xzcvczx (xzcvczx)]

This also occurs on osx, And if after closing the console reopening it you type in help() again kicad freezes

[Nick Østergaard (nickoe)]

This still happens in master:
Application: pcbnew
Version: (6.0.0-rc1-dev-238-gce3760438), 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
    OpenCASCADE Community Edition: 6.8.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_USE_OCC=OFF
    KICAD_SPICE=ON

[Wayne Stambaugh (stambaughw)]

I did some testing and I don't think there is much we can do about this. The python console (pyalamode) behaves the same way when run directly from the command line so its actually the console firing the busy cursor. The only difference when the console is run from the command line is that when the busy cursor is active, the console cannot be close until the help feature is closed (q). I don't know if we are doing something to change this behavior or if that is how the console behaves when run in a sub-process. I don't know if there is anything we can do about this.

[Michael Kavanagh (michaelkavanagh)]

Reading Wayne's comment, I'll mark this as incomplete so it expires if no one has any ideas? We tend not to leave bugs open that are caused by dependencies.

[Launchpad Janitor (janitor)]

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