Skip to content

feat: add default language setting - #230

Open
mxmgorin wants to merge 2 commits into
palsoftware:mainfrom
mxmgorin:feature/default-language
Open

feat: add default language setting#230
mxmgorin wants to merge 2 commits into
palsoftware:mainfrom
mxmgorin:feature/default-language

Conversation

@mxmgorin

@mxmgorin mxmgorin commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Description:
Adds a 'Default layout' option that makes the keyboard always start in a chosen language when a new text field is opened, instead of keeping the last used. Defaults to "Last used" to keep current behaviour.

Reason:
Currently, after switching language, it stays until you manually switch back. If you type mostly in one language, this means constantly changing the layout. Pinning a default language makes the keyboard reliably return to primary language on each typing and you always know which language is currently selected.

Screenshot_20260604-001421.png

@mxmgorin
mxmgorin force-pushed the feature/default-language branch from 7076cfc to 864abae Compare June 3, 2026 20:20
@mxmgorin
mxmgorin force-pushed the feature/default-language branch from 864abae to 4f5cf20 Compare June 3, 2026 20:39
@pzauner

pzauner commented Jun 4, 2026

Copy link
Copy Markdown
Collaborator

Great addition, will review this soon!

@pzauner

pzauner commented Jul 18, 2026

Copy link
Copy Markdown
Collaborator

Merge has some issues:
The new preference key is missing from the backup/restore schema.
When the selected layout is deleted, renamed, or hidden, an invalid selection remains stored.
The change is tied to onStartInputView; when using a hardware keyboard, onStartInput is the more reliable lifecycle hook.
Registering additional subtypes and the immediate switch occur directly one after the other. The Android subtype list may still contain the old state during this process.

I can fix them myself though.

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.

2 participants