The option in System -> Keyboard Options -> “Use Command key as Control key” is missing in the PTR. I don’t have access to beta. Is it missing there too, and is this going away in SL? The functionality right now is as though that option were unchecked, which is messing up my macros.
The command key is independently bindable in the 9.0 client. You should be able to use the cmd keyword in macros and bind cmd + <key> hotkeys in the normal hotkey UI, independent from the ctrl bindings/macros.
1 Like
So basically now mac has more keybinds than windows, because they have that stupid windows key not command 
1 Like
Hrm. Does this mean 9.0 has OS shortcuts disabled by default? That’s the only safe way to allow CMD key combo binding. I’d miss being able to CMD-A/V for my chat pastes.
I’m finding that the Command key isn’t responding at all in game for me on the PTR. Command + [key] is already bound to several of my action bar keys and shows up as such on the action bar and in the keybinds menu, but now it’s totally non-responsive when I try to use it in game or to re-bind keys with command+[key]. In previous iterations it was fine so this must be a relatively recent bug.
I just tried the PTR myself and the basic shortcuts seem to work at least (CMD-A, C, V). What are your exact Command key shortcut binds? That info might help Blizzard determine if there is a conflict on your side or an omission on their side. It could be that certain combinations are marked as off limits because they are OS shortcuts.
It’s my main modifier for my entire lower action bar, so there are several. Looking down at the keyboard from left to right: Command+D - Command L; next row up Command+T - Command+O; next row up Command+5 - Command+0. Cut/paste and other text functions operate separately when your cursor is within the chat box (and actually do work for me in the chat box), so I don’t think it’s an interaction going on there.
The “Disable OS Shortcuts” setting still exists and everything should work as it did in the 8.x client with it on and off I believe. Cut, Copy, Paste, and Select All hotkeys should work in chat/text contexts as expected in all cases. You may need to use “Disable OS Shortcuts” to be able to use some bindings (such as CMD+TAB or any mission control hotkeys) and CMD+H and CMD+M are never bindable, but both of those caveats were true with the “Use Command key as Control key” setting as well.
If any of what I said is not true, it’s a bug that can get fixed up
1 Like
CMD+H not being bindable is news to me, as I currently have it bound on live! But in any case it does seem to be a bug on PTR; I have submitted a report.
Actually, I went to verify everything is working ok and it looks like Command key binding broke at some point recently. I’ll get it fixed up in an upcoming 9.0.1 build.
I also verified CMD+H and CMD+M are unbindable on 8.3.7 with any combo of “Disable OS Shortcuts” and “Use Command key as Control key”. Blestis, are you sure you’re not remapping the command key to something else in the system preferences. Based on the fact CMD key is working for you in the current PTR and that you can use CMD+H on live, it sounds like you’re not actually using the command key.
3 Likes
CMD-H not being bindable may be related to a dual fix/accessibility change in the new client.
I was informed that in addition to the accessibility fix, CMD-H and CMD-M are always available to prevent players from running into situations where they are unable to exit the game when it appears to be locked up. As a result, those two are hardcoded to remain as OS shortcuts. If I’m wrong on this I’m sure Rommax will chime in.
Edit: Rommax beat my post. Yay for being a Grade F typer on touchscreens. 
CMD is working on PTR only for chat functions (cut/paste/copy), but not other in-game actions (spells or menu shortcuts). Thanks for putting it in to get the bug sorted! On live with “use CMD as CTRL” selected, I’m definitely able to use CMD+H (along with the other CMD binds I have set up – which are of course technically listed as CTRL in the key binds menu on on the action bar) without an issue. I don’t know why H it works for me if it’s not supposed to, but I’m positive it does (I’m logged in live rn using it – hope it stays that way!). CMD+M/CMD+TAB, however, don’t work, for the reason you describe.
EDIT: Looks like I did some OS shortcut shenanigans way back so I could use CMD+H when I realized I needed it for my setup, which I had forgotten about. I made a unique “Hide Window” command that replaces CMD+H only while playing WOW, thus freeing up that key bind for my bars.
This is not a good change, If I play in Mac and PC, now I need to diferents key binds. I miss the old devs
3 Likes