Footprint choice wizzard dialog hidden behind blocked other window, waiting for chosen wizard parameters and display

[LordBlick]

If you use python scripting footprint wizard dialog, always you must search for wizard selection window, usually hidden behind already not yet used widow for input parameters and view result.
Attached picture illustrates issue.

[LordBlick (lordblick)]

Some typo in picture corrected.

[jean-pierre charras (jp-charras)]

This issue is certainly related to Bug #1458449 and I am thinking it is an event loop issue.
It happens only on a few Window Managers.

It does not does not happens on my installs ( Windows 7, Ubuntu 10.04 with KDE, Ubuntu 14.10 with Unity)

What is your WM?

The window titled Footprint Builder Message is not awxDialog (it is a miniframe).
 the footprint selector dialog is the only one wxDialog, ans therefore should be on top.

Can you give it the focus ( move it and/or select a footprint? )
If no, What is the frame which has the focus?

[LordBlick (lordblick)]

WM: XFCE4
All windows I can move except „Footprint Builder Message”.
Footprint selector? Maybe wizard plugin selector?
I can select wizard plugin, then all back to normal.
If I click on „Select wizard to use…” in „Footprint wizard" window, then wizard plugin selector stays on top and that is OK. Wrong behavior comes from click on „New footprint using wizard” in footprint editor, maybe it is race condition which window is showed first.
My opinion:
Independently there is no reason to show „Footprint Builder Message” and „Footprint wizard [no wizard selected]” before selection done, it creates unnecessary confusion from the herd windows on the screen (May be: main app, pcbnew, footprint editor and 3 windows of footprint wizard, where only one needs user reaction…). After click on „Select wizard to use…” those windows should be hidden until wizard plugin selection done. If selection canceled, we return to footprint editor, where we can we call choice of wizard plugin again.

[LordBlick (lordblick)]

Build information:
BZR6162 release build
wxWidgets: Version 3.0.2 (release,wchar_t,compiler with C++ ABI 1002,GCC 4.9.3,wx containers,compatible with 2.8)
Platform: Linux 4… x86_64, 64 bit, Little endian, wxGTK
Boost version: 1.58.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=OFF

[LordBlick (lordblick)]

It is different issue than https://bugs.launchpad.net/bugs/1458449 All is fully functional, no doubled windows, but only top window is unappreciated, if called from footprint editor.

[jean-pierre charras (jp-charras)]

Try rev 6163.

[LordBlick (lordblick)]

In fact it is not wizard, but generator, wizard usually has at the minimum few steps…

[jean-pierre charras (jp-charras)]

What I *need to know* is if rev 6163 fixes the fact the wxDialog to choose the python script wizard wasnot on top of the other frames.
The bug 1458449 is the same (wxEventLoop issue when switching from a loop to an other)

[LordBlick (lordblick)]

OK, thanks for a fix, its more simpler than my imagination (User needs to guess that still must do a second click to select the plugin, which is not so obvious), so I make it as wishlist… ;) Maybe sometime I find time to bring it to true…

[Jeff Young (jeyjey)]

Most of this has been fixed, except that the build messages box still "falls behind" the front window on OSX.

[KiCad Janitor (kicad-janitor)]

Fixed in revision 8badfea17ad0ef998e052c1ff794656d2318271c
https://git.launchpad.net/kicad/patch/?id=8badfea17ad0ef998e052c1ff794656d2318271c