KiCad - the KiCad Bridge

1.0.40: 1.0.40: the bridge no longer crashes Windows Explorer. When a KiCad window reached the foreground during a verb, the bridge sent it behind and then forced the user's previous window back to the front (thread-input attach, ShowWindow, BringWindowToTop, SetForegroundWindow). Clicking a KiCad taskbar button makes the TASKBAR that previous window, so the bridge did this to the Windows 11 taskbar and Explorer crashed inside Taskbar.View.dll (0xc0000005), twice in a row on AdomLapper and earlier on winvm. Now: a shell window (taskbar, Start, desktop, anything owned by explorer.exe) is never recorded as the user's window and never forced to the front. And the user's own click is recognised properly: any input in the last 1.5 s with the cursor on the taskbar or on the KiCad window means the user brought it up, so it is left alone; the old test polled the mouse button every 120 ms and missed quick clicks, which is why a clicked KiCad window was sometimes sent away again. This bug is in every earlier native build, including public 1.0.37.