Merge lp:~davidmhewitt/wingpanel-indicator-keyboard/fix-1650986-xml-config into lp:~wingpanel-devs/wingpanel-indicator-keyboard/trunk
Status: | Merged | ||||
---|---|---|---|---|---|
Approved by: | Danielle Foré | ||||
Approved revision: | 67 | ||||
Merged at revision: | 66 | ||||
Proposed branch: | lp:~davidmhewitt/wingpanel-indicator-keyboard/fix-1650986-xml-config | ||||
Merge into: | lp:~wingpanel-devs/wingpanel-indicator-keyboard/trunk | ||||
Diff against target: |
125 lines (+35/-55) 2 files modified
src/CMakeLists.txt (+2/-1) src/LayoutsManager.vala (+33/-54) |
||||
To merge this branch: | bzr merge lp:~davidmhewitt/wingpanel-indicator-keyboard/fix-1650986-xml-config | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Santiago (community) | code | Approve | |
WingPanel Devs | Pending | ||
Review via email: mp+317703@code.launchpad.net |
Commit message
Load XKB config names from evdev.xml instead of evdev.lst
Description of the change
The list of XKB keyboard configurations was being read from evdev.lst. All documentation online about how to create keyboard maps refers to creating them in evdev.xml.
I checked and both files contain the exact same base configurations for every language and keymap. But, it's likely that any custom or new keyboard maps will be added to the XML files.
This branch should have no functionality impact whatsoever for the average user. But for the case in the attached bug, where custom layouts are not displayed, this branch resolves that.
To be able to add a custom keyboard map, you must be running a version of the keyboard plug that supports loading configs from XML too. See the following branch:
https:/