Reconsider adaptive touch correction? Slimmer proposal with details
維護者通常 1 天內回覆
評估
研究方向
This is a design proposal, not a ready task. Read the maintainer's earlier concerns in #671 and the open pull request #680 before anything else. The payload names InputLogic as the core file the change touches, plus a separate statistics package with 17 tests. Done means the maintainers have agreed on a design, not that a patch exists. Wait for that decision before starting code.
由索引模型根據 Issue 內容生成。
描述
Thanks again for reviewing #671. I'd like to explain the feature in more detail and offer a much slimmer version, because I think it addresses your concerns.
Why it matters
I'm an experienced, heavy phone typist. Still, over ~1,250 recorded touches about 13% landed on a neighboring key — roughly every 8th letter. And it's systematic, not random: "a" hit as "s" is consistently my most frequent miss. A fixed, per-user offset like this is exactly what adaptive touch correction fixes, and as far as I know it has been standard in mobile keyboards for many years.
What it does
The keyboard learns where this user actually touches each key, based on the words they finally commit (including reverted autocorrections and self-corrections). Once a key has enough data (30+ touches), a touch near the border between two keys is assigned to the key the user most likely meant. The shift is capped to a fraction of a key width, and the dictionary receives the corrected coordinates too.
Your concerns
- Determinism: same data, same key. It only differs from today near key borders and only after enough data. With the feature off, the exact current code path runs.
- Latency: per touch a few arithmetic operations on cached offsets, no I/O.
- Muscle memory: it adapts to the user's muscle memory instead of changing it.
- Code footprint: of the ~1.5k lines, ~1.45k are in a separate package (model, statistics screen, 17 tests). Core changes are ~115 lines.
Slimmer proposal
- One single switch ("Adapt to my typing"), fixed strength, no other settings.
- Move all recording logic out of InputLogic into the separate package, leaving ~60 lines of hooks in core.
- Optional: drop the statistics screen if you prefer.
If you're still not convinced, no problem — I'll keep it in my fork.
- 主要語言
- Kotlin
- 星號
- 1k
- 分支
- 59
- 平均合併
- 13 小時 21 分鐘
- 30 天內合併 PR
- 48
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
LeanBitLab/LeanType 的其他 Issue
-
Voice input fails in browser address bars due to incorrect password field detection (v4.2.9, follow-up to #516)可能已有人在做 @LeanBitLab 於 2 天前認領。 未關閉bug
難度 2/5 1-3 小時 新手友好度 76/100
LeanBitLab/LeanType#713 · 1 則留言 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 65/100
LeanBitLab/LeanType#423 · 1 則留言 ·
維護者通常 1 天內回覆
-
enhancement
難度 3/5 1-2 天 新手友好度 70/100
LeanBitLab/LeanType#724 ·
維護者通常 1 天內回覆
-
bug
難度 3/5 1-2 天 新手友好度 55/100
LeanBitLab/LeanType#723 ·
維護者通常 1 天內回覆
-
enhancement
難度 3/5 1-2 天 新手友好度 56/100
LeanBitLab/LeanType#721 ·
維護者通常 1 天內回覆
查看 LeanBitLab/LeanType 的全部 Issue
相似的 Issue
-
staticAssetsPath follows symlinks outside the directory on Windows可能已有人在做 @ybelMekk 今天認領。 未關閉bug security findings
難度 2/5 1-3 小時 新手友好度 84/100
navikt/mock-oauth2-server#1132 ·
維護者通常 1 天內回覆
-
a:plugin-description
難度 1/5 1 小時以內 新手友好度 76/100
gradle/plugin-portal-requests#319 ·
-
難度 2/5 1-3 小時 新手友好度 65/100
SimonHalvdansson/Harmonic-HN#399 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
-
[Request] 李跳跳未關閉request-adaption
難度 2/5 1 小時以內 新手友好度 78/100
BetterAndroid/android-notification-icon-project#799 ·
維護者通常 1 天內回覆