Custom shortcuts - unintuitive behavior

I can reproduce this using xenial 16.04 with the german translation.

Reproduction steps:

 * Execute "unity-control-center keyboard shortcuts" in a terminal.
 * In the left menu select "own shortcuts" (or equivalent translation).
 * Press the + to add a new shortcut. Name it "Test" and ad some valid command like "unity-control-center"
 * Select your new entry

What happens: The edit menu opens to edit the name and command

What should happen: The design changes indicating that the shortcut is recorded.

Please note: This works fine with the predefined shortcuts in "unity-control-center keyboard shortcuts".

Best Regards

Vej

On 2017-02-23 21:34, Vej wrote:
> * Select your new entry
>
> What happens: The edit menu opens to edit the name and command
>
> What should happen: The design changes indicating that the shortcut
> is recorded.

I wonder if there is a misconception floating around...

If you click on the word "Disabled" of the new entry (to the right), you are given the opportunity to enter a "new accelerator". Works fine for me (on 16.10).

So, Felix and/or Vej, can you please elaborate on what the problem is, or confirm that my suspicion is correct.

@Gunnar: You are right. Clicking on "Disabled" opens the window to record the shortcut.

Nevertheless we have a different behavior between the predefined shortcuts and the own ones. I consider it unintuitive, that the action for editing the own shortcuts is used to record predefined shortcuts. A better UI would keep them the same i.e. to perform no action when clicking on the name of a predefined shortcut.

I agree that there is room for improvement of the design. More intuitive (IMO) would be that it was just highlighted when you click it, as for the predefined shortcuts, and that the window for editing is opened when you double click or right click.