Member Avatar for Excizted

Hello,
I've been using Dvorak on my Linux machine for a long time, and I've finally convinced my sister to do the switch as well.

Using Microsoft Keyboard Layout Creator (MSKLC) I easily managed to install Dvorak layout, but shortcuts like Ctrl+C doesn't move, it's the same spot, so after moving the keys around I actually press Ctrl+J.

It's kinda hard when it comes to irregular shortcuts in other programs. Because the program will tell me to use Ctrl+B, but then I'd have to rethink that it actually is Ctrl+X.

How do I make a keyboard layout that works completely, and doesn't just affect the letter appearing when pressing the buttons?

Thank you! :)

  • 2 Contributors
  • 7 Replies
  • 260 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by caperjack

Dani AI

Generated

Short answer: MSKLC only changes the character mapping; it does not reliably change how programs interpret modifier+key shortcuts. As noticed, Windows delivers low-level key messages (WM_KEYDOWN) and most apps use accelerator tables or virtual-key codes to decide what Ctrl+X/C/V etc. mean — those mappings can be independent of the character that later appears. (learn.microsoft.com)

Why it feels inconsistent: some programs define accelerators by ASCII character, some by virtual-key codes, and some do their own input handling. The Windows APIs that translate between scan codes, virtual-key codes and characters (MapVirtualKeyEx / ToUnicodeEx) explain why behavior changes between apps and setups. That is why Ctrl+C can end up at a different physical key after installing a Dvorak layout. (learn.microsoft.com)

Workarounds that actually work in practice:

  • Use AutoHotkey to remap the shortcut combinations you care about. Example (put in a .ahk file and run AutoHotkey):
^j::Send ^c
^k::Send ^v
^q::Send ^x

This sends the usual Ctrl+C/Ctrl+V/Ctrl+X when the Dvorak-position keys are pressed. Run the script as administrator if the target app runs elevated. For a more complete/robust approach people either create fuller AHK scripts (temporary switch to QWERTY while Ctrl is held) or use a registry scancode map for global remaps (global but requires reboot). (documentation.help)

Notes and tradeoffs: registry scancode remaps are simpler and system-wide but permanent until changed and cannot be per-app; AutoHotkey is flexible and per-user but must run to be active. macOS has a built-in “Dvorak — QWERTY ⌘” style option; Windows does not, so AHK or firmware-level remapping (QMK/programmable keyboard) are the common solutions. For this explains why MSKLC alone didn’t fix shortcuts; for it’s one reason Linux often behaves differently out of the box. (en.wikipedia.org)

Recommended Answers

All 7 Replies

Member Avatar for caperjack

edit forget it

Edited by caperjack because: n/a
Member Avatar for Excizted

Daimn!

Member Avatar for caperjack

i was going to suggest linux forum because u use linux ,but seen you were
Using Microsoft Keyboard Layout Creator,what ever that is ,maybe someone will come along who uses
Microsoft Keyboard Layout Creator

Member Avatar for Excizted

I usually use Linux yes, where everything works perfectly, but on Windows by using MSKLC to make my keyboard layout, shortcuts remain at the physical location on the keyboard.

Member Avatar for caperjack

I usually use Linux yes, .

that why I was confuse confused ,why did you even mention linux in you post ,and if linux works so perfectly for you then why bother with windows .just my opinion .
i don't use many short cuts except copy paste

Member Avatar for Excizted

Well because working perfectly for me doesn't help my sister :)

Member Avatar for caperjack

Well because working perfectly for me doesn't help my sister :)

ok, thought you meant 2 different computer .lol

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.