Prefer AccountsService's InputSources
property instead of custom KeyboardLayout/XkbOptions
pair.
#70
Labels
Needs Design
Waiting for input from the UX team
Priority: Wishlist
Not a priority, but something that might be nice
Status: Confirmed
Verified by someone other than the reporter
Currently (inspecting the system bus) we keep keyboard state in two AccountsService interfaces:
At the same time, the standard org.freedesktop.Accounts.User interface has a InputSource property that can replace both KeyboardLayouts and XkbOptions properties from our custom interfaces.
The text was updated successfully, but these errors were encountered: