Francois Guibert
Francois Guibert
I'm observing the same behavior
I have this problem as well, but it's new. I've disabled all the other extensions and it's still happening. Anyone has a workaround? I'm in C++, Windows 11, latest Visual...
Might be similar to https://github.com/VsVim/VsVim/issues/3040, where I posted a potential fix.
Wow, crazy how I went digging into this issue just now, and you made the commit last week ;) So I tested it, on Win32, using `alcReopenDeviceSOFT`, `alcEventControlSOFT` and `alcEventCallbackSOFT`...
I have the same issue as well. It might be a conflict with another app, but there is no issue with the VIM extension of VSCode for example. EDIT: In...
It's me again. I've spent some time debugging the issue, and I have a local patch that fixes it, at least for me. I've never wrote F# or WPF code...
See https://github.com/VsVim/VsVim/issues/3040 for a potential fix
Just stumbled onto this issue as well. I cached the call myself but it would be better and more logical if the callable wasn't called multiple times in my opinion....
Same issue for me. I think the conclusion is that we shouldn't use `GameInput`, right?