Oh, I think it's a bit worse than that. Maybe this is a separate bug: When I edit the NAME of an existing custom shortcut, it gets assigned the keybinding of a DIFFERENT existing shortcut. I think everything is getting scrambled around.
(btw, I guessed at the package name; sorry)
Oh, I think it's a bit worse than that.
Maybe this is a separate bug: When I edit the NAME of an existing custom shortcut, it gets assigned the keybinding of a DIFFERENT existing shortcut.
I think everything is getting scrambled around.
(btw, I guessed at the package name; sorry)