Fix default bindings command string order

[pjrobertson]

Fixes #3054

[n8henrie]

Weird -- why does the order matter here, and how did you figure it out? Did you find some documentation somewhere?

[pjrobertson]

I think probably at some point we (I) updated NDHotkey which maybe change the orders that hotkey strings get written (I have a vague memory). The place to go for all these key bindings is that DefaultBindings.qskeysfile. If you look at the top, the key is QSSearchObjectView which means they are key bindings for all QSSearchObjectView (i.e. they work for QSSearchObjectView views. So then you go to QSSearchObjectView.m and find:

- (BOOL)handleBoundKey:(NSEvent *)theEvent {

In there, there's a check for NSString *selectorString = [bindingsDict objectForKey:theEventString]; which is doing a string comparison with the keys (keyboard shortcut strings like ⌘C ). I debugged that and found theEventString was coming back in a different order, so I flipped it :)