workman-layout / Workman

Workman keyboard layout
https://workmanlayout.org/
Other
905 stars 112 forks source link

Chrome keyboard shortcuts don't work #10

Open nstoddard opened 10 years ago

nstoddard commented 10 years ago

I installed Workman today on Windows 7 and it works everywhere except Chrome keyboard shortcuts. For instance, when I type ctrl+f in Workman, Chrome interprets it as ctrl+e, which is in the same place on QWERTY. I've used Colemak for a couple years with no problems so it seems like a bug in the Workman implementation.

I've tried restarting my computer, and reinstalling the keyboard layout. Neither helped. I've tested the keyboard shortcuts in a couple other applications besides Chrome and they seem to work.

Edit: I tried creating my own keyboard layout in the Microsoft Keyboard Layout Creator, based on Colemak with only a few changes, and the keyboard shortcuts worked fine in Chrome. This is a very strange bug.

Edit 2: After loading Colemak in the keyboard layout creator, I noticed that each key is given a name of the form VK_key, and Colemak has somehow moved these codes around. For instance, Colemak's D key is called VK_D, not VKG. However, I can't figure out how to use the keyboard creator to change the VK values with the keyboard layout creator. Workman uses the default QWERTY values for them, which seems to be the problem.

Hopefully final edit: I found an article about how to resolve this. After modifying the keys, you have to open the .klc file in a text editor and manually change the VK codes.

deekayen commented 10 years ago

Doesn't Colemak use something other than Microsoft Keyboard Layout Creator to generate and implement their layout? Perhaps it's time to add that to the Windows download options?

l8nite commented 10 years ago

+1 on this being an issue. I was able to apply the workaround @nstoddard identified (manually edit .klc file). Here's the fixed version: https://gist.github.com/l8nite/7101818

joel0 commented 4 years ago

PR #18 fixed this for the US and US-P layouts, by changing the scan codes like suggested by @l8nite . PR #49 will fix this for the UK and UK-P layouts.

I think this issue can be closed.