Repository navigation
カスタムキー編集の入力方式を従来順に戻す / Restore input-style order in the custom key editor - #1353
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
カスタムキー編集の「入力方式」で、新しく追加されたフリーフリックとQWERTYが従来の方式より先に表示されていました。
表示順を「1段フリック → ドーナツフリック → 2段フリック → フリック長押し → フリーフリック → QWERTY」に変更します。レイアウト内の選択肢の順序だけを変更しています。
検証:XMLの構造比較により、選択肢のID・ラベル・属性と他の要素が同一で、変更が並び順のみであることを確認。Lite Debugのビルドと既存のKeyEditorToggleValidationTest(1件)が成功しました。実機での確認は未実施です。
The custom key editor placed the newly added Free Flick and QWERTY options before the established input styles.
Restore the order: single-stage flick → circular flick → two-stage flick → flick with long press → Free Flick → QWERTY. Only the order of the choices in the layout changes.
Validation: structural XML comparison confirms that option IDs, labels, attributes and the remaining layout are unchanged. The Lite Debug build and the existing KeyEditorToggleValidationTest (1 test) passed. Physical-device verification has not been performed.