GAL: cannot double-click through disambiguation menu

[Chris Pavlina]

If you double-click on an object in pcbnew/GAL and a disambiguation menu appears, choosing the object in the menu only selects it, rather than executing the double-click action on it.

Application: kicad
Version: (2015-09-14 BZR 6200, Git e27fa50)-product debug build
wxWidgets: Version 3.0.2 (debug,wchar_t,compiler with C++ ABI 1002,GCC 4.2.1,wx containers,compatible with 2.8)
Platform: Linux 4.1.6-1-ARCH 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=ON

[Nick Østergaard (nickoe)]

This disambiguation menu you are talking about, is this the Clarify selection context menu?

[Chris Pavlina (pavlina-chris)]

Yes.

[Maciej Suminski (orsonmmz)]

I cannot even double click an item, if there is more than one item in the same spot. The first click invokes disambiguation menu, that is immediately disposed with the second click, which is received by the context menu.

The problem with double click event is that single click event arrives first, and afterwards there is a double click event, as it is impossible to foresee if the first click is just a part of double click. Any ideas how to solve it?

[Nick Østergaard (nickoe)]

Is this still relevant? There have been some fixes regarding this recently from Seth as far as I understand it.

[Seth Hillbrand (sethh)]

Yes. My fix applied only to the legacy canvas. I'm looking into a similar method for GAL. I'll assign this one to me for now.

[Seth Hillbrand (sethh)]

From the duplicate, while creating this delay, we need to look at configuring the delay time and not using the delay if there is no disambiguation required (or propagate the cross-probe based on the top stack until the delay)

[Seth Hillbrand (sethh)]

We've been living with this one for a while and the previous fix caused more bug reports. Probably best to come up with a full solution in 6

[KiCad Janitor (kicad-janitor)]

KiCad bug tracker has moved to Gitlab. This report is now available here: https://gitlab.com/kicad/code/kicad/-/issues/1832