[Bug] GLFW keyboard and linux xmodmap

[jakethesnake]

The key rebinding mechanics of xmodmap stopped working when I updated from 3.2.0 to 3.3.0, and it seems GLFW has had issues with it. Now I see that this might have been fixed with GLFW 3.3.5, which also comes with a bunch of other bugfixes. But alas lwjgl comes with 3.3.4, even the nightly build.

I don't know if I can update glfw natives by myself, but I think it's beyond me, sine they're .jars.

I guess I'm asking kindly for a GLFW 3.3.5 wrap.

[spasi]

LWJGL 3.3.0 includes GLFW 3.3.5, the release notes are wrong and will be fixed.

I'm not sure what issue you're referring to though and I don't see any recent fixes related to it.

[jakethesnake]

LWJGL 3.3.0 includes GLFW 3.3.5, the release notes are wrong and will be fixed.

I'm not sure what issue you're referring to though and I don't see any recent fixes related to it.

Ok, that's good, and back to square one then. The problem I have is a user on linux using xmodmap to swap Cntl and Caps lock. This used to work with an older GLFW, but now doesn't with the new one. I don't quite understand what I'm reading about xmodmap and GLFW, but they seemed they had a bunch of bugfixes in 3.3.5 that touched upon input, so I was hoping for that to solve it. I'm not sure this is a bug or intended behaviour and you now have to translate the scancodes or something.

FYI, GLFW.glfwGetVersionString() also returns "3.4.0 Win32 WGL Null EGL OSMesa VisualC DLL"

[spasi]

FYI, GLFW.glfwGetVersionString() also returns "3.4.0 Win32 WGL Null EGL OSMesa VisualC DLL"

That's because LWJGL-CI builds the master GLFW branch (currently at 3.4.0), not the "3.3-stable" branch (currently at 3.3.7).