[Feature Request] Improve clipboard clip editing mode and add character/clip counters (inspired by jbak2exp)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 25/100
Línea de trabajo
The payload names no source files or tests. Start with the clipboard clip editing mode in the suggestion strip, where the Save and Cancel buttons sit, and with the status bar where the character counter would appear. Done would mean a multi-line edit field showing the whole clip, plus the optional counters, but the request is open-ended and its screenshot placeholders were never filled in, so confirm the scope with a maintainer first.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Hello dear LeanType developers,
First of all, thank you for this excellent keyboard — I really enjoy using it.
I would like to suggest an improvement to the clipboard clip editing mode.
Current Behavior (The Problem)
Right now, when editing a clipboard clip — regardless of its length — the entire clip is placed in a single line in the suggestion strip, with the Save and Cancel buttons at the very end of that line.
For clips longer than a few words, this is very inconvenient:
You have to scroll a lot.
You can't see the whole clip at once — only a small fragment.
Proposed Improvement
I'd like to suggest an approach similar to the one used in the jbak2exp keyboard (link):
Multi-line editing field: When editing a clip, it should be placed in a separate input field (a separate window) with multiple lines, so the entire clip is visible at once. (See attached screenshot.)
Clip counters and indicators: I'd also like to draw your attention to how jbak2exp displays:
The total number of clips and the clip limit in the buffer (e.g., 250/400 in the screenshot).
The character count for each clip (e.g., 156-86-125-104 in the screenshot).
The character count for the current input field (the red indicator showing 156 in the status bar in the clip editing mode screenshot).
Why This Would Be Useful
I used jbak2exp for a long time, and these features are genuinely convenient:
The character counter for the current input field is especially useful when a field has a length limit but doesn't display its own counter.
Seeing the full clip while editing makes editing much faster and less error-prone.
Request
Please consider changing the clip editing mode as described above, and optionally adding these counters/indicators to LeanType.
Thank you for your time and for considering this usability improvement. I really appreciate all the work you put into this keyboard!
Screenshots
[ВСТАВИТЬ СКРИНШОТЫ СЮДА]
Additional Notes
I've attached screenshots from jbak2exp showing:
The multi-line clip editing window.
The clip counters (250/400) and per-clip character counts.
The current input field character counter (red 156 indicator).
Environment
LeanType version: beta-429-5 / beta-429-6 (or whichever you're currently using)
Android version: 13
Device: Poco X3 NFC
ROM: Baikal OS (custom ROM)
Locale: ru_RU
- Lenguaje dominante
- Kotlin
- Estrellas
- 1k
- Forks
- 59
- Merge medio
- 13 h 11 min
- PR fusionados (30 d)
- 47
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de LeanBitLab/LeanType
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
LeanBitLab/LeanType#713 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
LeanBitLab/LeanType#423 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Crush ReportAbierto
Dificultad 3/5 1-2 días Aptitud para principiantes 20/100
LeanBitLab/LeanType#715 ·
Los mantenedores suelen responder en 1 día
-
Text Expander/cursor-handling bugPosiblemente ocupada @LeanBitLab la tomó hace 2 días. Abiertobug
Dificultad 3/5 1-2 días Aptitud para principiantes 62/100
LeanBitLab/LeanType#703 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
LeanBitLab/LeanType#699 ·
Los mantenedores suelen responder en 1 día
Todos los issues de LeanBitLab/LeanType
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
lugassawan/swe-workbench#823 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
Droid-Deck/DroidDeck#1355 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
IronCoreLabs/ironcore-alloy#351 ·
-
Lovelace refine Taak
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
MinBZK/MijnOverheidZakelijk#1383 ·