AppFlowy-IO / AppFlowy-IO/AppFlowy

[FR] allow unassigning shortcut

Abierto
#5,794 2 comentarios 2 reacciones 1 asignado Asignado a @MayurSMahajan Ver en GitHub
improvements shortcuts
Lenguaje dominante
Dart
Estrellas
76.6k
Forks
6k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### Description

Let the user unassign an existing shortcut. Don't force them to have shortcuts assigned to every function if they don't want to. It could be as simple as adding a little ❌ button near the ✏️ one, and it would just clear out the key combination.

If the user wants to assign a shortcut to that later, they always can. But right now we only can assign a different key combination.

### Impact

Like many people in the world, I don't use an American QWERTY keyboard layout. So it can happen quite often that pressing a specific combination of keys is needed for me to write a common character for my language. Which can become hard to do when a software catches those key combinations as a function shortcut. So the only solution is to either change the shortcut's key combination to something else, or sometimes to remove the shortcut because you don't need it and prefer saving your shortcut layout for something else.

In Appflowy for example, ⎈ Ctrl⎇ AltE is used to invoke the emoji picker, but I need that very same combination of keys to write a very common character in my native language.

So I went to the shortcuts' editor, and since I don't see any use of that emoji picker for me (Windows' native picker is more furnished and in non-conflicting shortcut), I tried deleting the shortcut, but it's impossible. I had to replace it by a stupid combination that I am sure I will never use in any other occasion:

![image](https://github.com/user-attachments/assets/a0281fa3-531b-4529-b6d0-013d9f9a186c)

If I could just delete it, there would be no problem here, in addition to be more user-friendly.

### Additional Context

_No response_

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.