Merge lp://qastaging/~osomon/unity-2d/launcher-items-keyboard-shortcuts into lp://qastaging/unity-2d/3.0

Functionally there's only one corner case where it doesn't work: if the shortcut key is some accented character, it's not displayed as a shortcut. For example if you edit /usr/share/unity/places/applications.place and make the shortcut key "é", it will not work (the key is not even grabbed).

134 + if (value.size() == 1) {
135 + QChar c = value.at(0);
136 + if (c.isLetter()) {
137 + Qt::Key key = (Qt::Key) (Qt::Key_A + (c.toLower().toAscii() - 'a'));
138 + entry->setShortcutKey(key);
139 + }
140 + }

I am a fan of the principle "be strict in what you emit and relaxed in what you accept", and in this case if the string length is larger than 1 character, why don't you just pick the first character and emit a warning.
Or if you prefer just emit a warning and set no shortcut. But don't just silently do nothing.

It's still not working. I set the shortcut to "é" (one single accented character), and I get this warning message: unity-2d-launcher: [WARNING] void Place::setFileName(const QString&): Invalid shorcut key (should be one single character): "é"

This is very likely because your text editor, when you are typing "é", is in fact inserting two characters (0xc3 + 0xa9) instead of one (0xc9). The visual representation is the same, but the underlying unicode representation isn’t, and as a consequence the string extracted from the place file is too long. At least the code now prints out a warning, it doesn’t ignore it silently.

Still, if you use an hexadecimal editor to set the shortcut to the correct unicode character (0xc9), grabbing the key fails lower down the stack with the following warning:

    Could not convert "É" to an x11 keysym

This happens during the conversion from a Qt::Key to an X11 keysym in the constructor for Hotkey. I’m trying to figure out how to fix the conversion.