Doug Binks
I would see if you can use raw mouse input as per the workaround.
Do you know if `glfwRawMouseMotionSupported()` returned true?
Thanks - that's annoying since it worked in my testing, though I was using a Windows machine as the host at the time.
Do note that I don't think there's much we'll be able to do with this in GLFW, hence why this is marked as external. At least the issue I observer...
If this is RDP related then it is potentially related to #1276 and the fix #2431 does not resolve your issue. To debug this it would be handy to know...
Thanks. My guess is that the RDP workaround only works from a Windows RDP client. I have opened #2798 for this.
You might want to check what is going on in the `updateFramebufferTransparency` function: https://github.com/glfw/glfw/blob/master/src/win32_window.c#L372-L405 You can use the `gears.c` example code to test this, as it sets a transparent framebuffer....
@orange451 does using `glfwSetWindowAttrib` to update the `GLFW_FLOATING` attribute when your application changes focus work as a solution for you?
The branch you have based your PR from is the `ci` branch, hence why this PR is proposing to merge to that branch. We can change the branch we merge...
The GFLW API currently has [glfwGetWindowMonitor](https://www.glfw.org/docs/latest/group__window.html#ga4d766499ac02c60f02221a9dfab87299) which returns the handle of the monitor that the specified window is in full screen on. So if this returns `NULL` the window is...