Luke

This also reproduces for me for Python 3.12 and wxPython 4.2.1. FYI, C++ wxWidgets works correctly, even without the MacOS bundle (unless it's run from within VSCode, but that seems...

@kk7ds I was referring to C++ wxWidgets when I mentioned VSCode. I remember I had this problem before with my C++ wxWidgets applications when running from VSCode, but I checked...

@swt2c as I said, I've checked 3.2.0 and it works correctly. If you have `cmake` and a C++ compiler, you can check it yourself. Here's your `CMakeLists.txt`: ```cmake cmake_minimum_required(VERSION 3.14...

@swt2c no problem, just give me the exact wxWidgets commit, and I will test it for you.

@swt2c On my machine, C++ apps compiled with `a812fffda3fe686c94e24bff27e8effd96e4de64` or `b97aee4` both work correctly (the window shows up on top when the app is run from the terminal). Python apps...

It seems that using older version of the mentioned package fixes the problem (5.2.1 instead of 6.0.0 which is installed by default): ``` ```

> Not a great position. Can’t believe you’re recommending not upgrading to macOS 15! MS has known that it would be in this position for best part of 3 months...

The actual file does not exist. It seems CMake does not generate it.

> > **Removing `@CMakeFiles\\main.dir\\main.cpp.obj.modmap` from `compile_commands.json` fixes the problem.** > > Can you show a log of this working case? ``` [START][2024-05-17 09:41:09] LSP logging initiated [WARN][2024-05-17 09:41:09] .../lua/vim/lsp.lua:1636 "buf_attach_client...

So we have three options: 1. I'm lying 2. I'm making some mistakes along the way 3. There's some heuristics `clangd` that causes it to parse the `compile_commands.json` in such...