Prevent first-keystroke UI stalls by suppressing WM_GETOBJECT on the launcher window

[Copilot]

Typing the first character could freeze Flow Launcher for ~15 seconds on affected systems. The stall was traced to the main WPF window servicing WM_GETOBJECT and entering the UI Automation provider path on the UI thread.

• Main window message handling

  • Intercept WM_GETOBJECT in MainWindow's existing HwndSource hook.
  • Mark the message as handled and return immediately so the launcher window does not enter WPF's synchronous automation-provider path during typing.
  • Scope is limited to the main search window; existing handling for other window messages remains unchanged.

• Behavioral boundary

  • Only WM_GETOBJECT is suppressed.
  • Other messages continue through the current WndProc switch unchanged.

• Regression coverage

  • Add a focused test that verifies the suppression predicate matches WM_GETOBJECT and does not suppress unrelated messages.

private const int WmGetObject = 0x003D;

private IntPtr WndProc(IntPtr hwnd, int msg, IntPtr wParam, IntPtr lParam, ref bool handled)
{
    if (msg == WmGetObject)
    {
        handled = true;
        return IntPtr.Zero;
    }

    // existing message handling...
}

• Fixes BUG: Flowlauncher freezing after typing in one character #4522

[Jack251970]

@codex Review it

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 81ac6c3896

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Do not swallow every WM_GETOBJECT request

When Narrator, a screen reader, or another UI Automation/MSAA client queries the launcher, it relies on WM_GETOBJECT to obtain WPF's accessibility provider. Returning zero with handled = true prevents HwndSource from servicing every such request, making the query box and results—including the explicitly configured AutomationProperties.Name in MainWindow.xaml—unavailable to assistive technology. The stall mitigation must preserve normal accessibility-provider requests rather than unconditionally consuming this message.

Useful? React with 👍 / 👎.