Project

General

Profile

Actions

Emulator Issues #5324

closed

Keyboard shortcuts behave incorrectly

Added by pauldacheez over 12 years ago.

Status:
Fixed
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

I haven't noticed until now, but it seems that the wxWidgets 3 update has introduced at least one regression.

Previously, pretty much every keyboard shortcut in Dolphin required you to hold the Command key and press the other key. Now, one just needs to press that other key. The menus in the menubar reflect this as well.

For example, to pause emulation you used to press Cmd+P. Now you just press P. This is quite irritating when these shortcuts overlap with your button mappings.

I don't know if Windows/Linux are affected.


Related issues 1 (0 open1 closed)

Blocks Emulator - Emulator Issues #5504: Dolphin 3.5 bug trackerFixed

Actions
Actions #1

Updated by parlane over 12 years ago

Check your keyboard is not broken :P

Actions #2

Updated by pauldacheez over 12 years ago

My keyboard's not broken. C'mon, I'm not THAT clueless, parlane. ಠ_ಠ

Actions #3

Updated by parlane over 12 years ago

Haha my control key gets stuck sometimes and exactly what you described happens. I don't have a mac, so I am just filling the issue with mild humour!

shuffle2 can you test this on your vm?

Actions #4

Updated by Anonymous over 12 years ago

What is the hotkey actually set to?

Actions #5

Updated by parlane over 12 years ago

Do you mean in your vm?

Or cmd+p for pause.

Actions #6

Updated by skidau over 12 years ago

I have just noticed that the debugger hotkeys (F9, F10, F11) no longer work under the Windows build. Similar behaviour is seen, i.e. pressing F10 activates the debugger menu instead of "Step Over".

Actions #7

Updated by skidau over 12 years ago

pauldacheez, are you running with Render to Main Window or are you using a separate game window?

Actions #8

Updated by pauldacheez over 12 years ago

I use Render to Main Window, but the bug appears for me in either mode. (Not being a debug type of guy, I haven't tested the debugger hotkeys.)

Actions #9

Updated by pauldacheez over 12 years ago

I don't want to be rude, but is anyone workin' on this? I'm tired of accidentally hitting W and being booted out of my game every time I miss the E key.

Actions #10

Updated by pauldacheez over 12 years ago

...Turns out, I never knew the Hotkey Settings window existed. And now that I do, I found some things out:
-If it lists Cmd+[key], you get the wonderful bug I started this issue about.
-Pressing Cmd+[key] makes it claim that I just pressed Ctrl+[key]. I still use the shortcuts with Cmd+[key], though.
-All key combinations shown in the menubar menus reflect the true buttons required to trigger the shortcut.
-Pressing the actual Control key makes it say Control, and it doesn't treat it as a modifier key, which means I can easily be an asshole and set someone's Control key to stop emulation.
-Pressing the Fn key makes the space blank, but it still registers, and follows all the rules of the Control key. Ugh.
-THERE IS NO WAY TO "CLEAR" A BUTTON. WHY.

So, tl;dr, I figured out my problem. I dunno about skid's, though.

Actions #11

Updated by skidau over 12 years ago

I couldn't reproduce mine either later on. I might have fallen into the same trap.

Actions #12

Updated by pauldacheez over 12 years ago

For reference:
"-THERE IS NO WAY TO "CLEAR" A BUTTON. WHY."
I was wrong - trying to set something to Space clears it.

Actions #13

Updated by delroth over 12 years ago

  • Status changed from New to Accepted

This bug on OSX 10.7 on a friend's laptop. Adding to the 4.0 blockers: it's a BIG UI annoyance (can't use the default mapped GCPad keys because they conflict with the emulator hotkeys).

Actions #15

Updated by pauldacheez over 12 years ago

Since it was never stated here: this happens on a fresh install of Dolphin, not just one with config files from before wxw3 (rd15740daf124).

This also seems to affect some keyboards with non-standard keys on Windows - see Issue 5537.

Actions #16

Updated by delroth over 12 years ago

  • Status changed from Accepted to Fixed

This issue was closed by revision 174c1b00f80b.

Actions

Also available in: Atom PDF