Skip to content

2段フリックの出力文字が消える問題を修正 / Fix lost two-step flick outputs - #1368

Merged
KazumaProject merged 2 commits into
devfrom
codex/fix-two-stage-flick-outputs
Nov 18, 2026
Merged

KazumaProject merged 2 commits into
devfrom
codex/fix-two-stage-flick-outputs

Conversation

@KazumaProject

Copy link
Copy Markdown
Owner

日本語

2段フリックの編集機能を再有効化した後も、キーの確定処理では TWO_STEP_FLICK が既定の分岐に進んでいました。この分岐が通常入力と長押し用の割り当てを削除するため、「完了」の後にキー編集を開き直すと出力文字が空欄になっていました。

TWO_STEP_FLICK を既存の保存処理に戻し、通常入力と長押し用の割り当てを編集中のレイアウトに保持して、再編集時に読み込めるようにしました。

検証

既存のビルド成果物を依存に使い、変更対象のKotlinソースをコンパイルしてJUnitを実行しました。追加した回帰テストで修正前の出力消失を再現し、修正後は KeyboardEditorViewModelFlexiblePlacementTest の86件すべてが通りました。

English

After two-step flick editing was re-enabled, the key update still routed TWO_STEP_FLICK through the default branch. That branch cleared both normal and long-press mappings when users tapped Done, so the outputs were blank when they reopened the key editor.

TWO_STEP_FLICK now uses the existing mapping save path. Both sets of outputs stay in the layout draft and can be loaded when the key editor opens again.

Verification

Compiled the affected Kotlin sources against existing build artifacts and ran JUnit. The new regression test reproduced the lost outputs before the fix. All 86 tests in KeyboardEditorViewModelFlexiblePlacementTest passed after the fix.

@KazumaProject
KazumaProject merged commit f998ab5 into dev Nov 18, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant