Pokechu22
commented
6 years ago After some further testing, there are two issues. One is that MOUSE_VIRTUAL_DESKTOP is weird, but that's not all. I've implemented the same thing from the DirectXTK commit (Pokechu22@92380fa), but that doesn't actually work right. The cursor moves fine for a bit, but when it gets to the edge of the monitor, it stops.
It seems that SetCursorPos doesn't work right when the cursor is hidden via SetCursor(NULL), so the re-centering logic isn't working. I've verified that by adding another key to the cursor test (this is not in the previously linked commit):
case GLFW_KEY_M:
{
int width, height;
glfwGetWindowSize(window, &width, &height);
glfwSetCursorPos(window, width / 2, height / 2);
break;
}When the cursor is visible, it moves back to the center and moving it around starts from the center. However, when it is hidden (not disabled), the tracking lines move to the center but the actual cursor does not. I suspect that this is a special behavior for the NULL cursor, and will try using an invisible custom cursor instead.
LiliumAtratum
flriancu
dougbinks
OS and version: Windows 10 64-bit Release or commit: Tested both 617a322bd88c1b27f1fd7d05dc3723b6c5461a68 and the version comes with LWJGL 3.1.2 (2f5e2303380d084ab9b097765d34f98504324d65 it seems)
When connected over RDP, disabled cursor input doesn't work correctly; the cursor goes far off the screen (causing rapid rotation if mouse input is being used for that -- e.g. the
waveexample program). (This was originally reported as MC-126875).To reproduce:
cursortest. Enable RDP connections to your machine.cursortest.This doesn't happen when connected locally.
Here's the output provided by the program:
I did do some debug logging of what the raw
WM_INPUTevent looked like. On my local machine, the flags value is0and the positions are0 4or similar. However, when connected via RDP, the flags value is3and positions are very large (e.g.9984 12588).3isMOUSE_MOVE_ABSOLUTE | MOUSE_VIRTUAL_DESKTOPper the documentation on the RAWMOUSE structure, but unfortunately it doesn't explain howMOUSE_VIRTUAL_DESKTOPis supposed to be handled.I have found some other sources though. This StackOverflow post gives an example of what works for them (but the author admits that it's not from any documentation). I also found Microsoft/DirectXTK@ef56b63f3739381e451f7a5a5bd2c9779d2a7555 which seems to be a case of them fixing the same issue. However, I haven't had time to experiment with this yet (if I do get it working, I'll try to submit a pull request).