GNOME Bugzilla – Bug 640774
For some reason I can't add more than 4 layouts
Last modified: 2013-05-06 07:37:33 UTC
For some reason I can't add more than 4 layouts. If this is some limitation of the implementation we should indicate this to the user somehow.
I thought by now everybody knows that XKB does not allow more than 4 groups. If you want to indicate that to the user - ok, let's do it. How? All I can do is disable the "add" button.
There are multiple ways to do this, but we'll run into trouble if we merge input sources selection with keyboard layouts selection. In the meanwhile, we could: - disable the "+" button - show an error when trying to add a 5th layout Is removing the limit from XKB something that can be done? It would be much easier than trying to work-around the problem...
No, the limit is hardcoded on the protocol level. 2 bits. X11 protocol is a holy cow, as you know. Currently, the button + is disabled when N(layouts)=4.
We know that, but we'll need to have an error message instead (explaining that it's technically not possible). I didn't realise that the configuration panel was already disabling the '+' button.
Jon, can you think of a good error message for this problem?
"Four layouts should be enough for anyone." ;) As a rule of thumb if you need to present such text something is wrong either in the code or in the presentation. Ideally we could communicate this visually. One way to do this might be to have a limited number of "slots" where layouts are added to them explicitly. [ English ] [ Russian ] [ Add layout ] [ Add layout ] Or we could communicate this with text using something like: "2 of 4 layouts" or even a segmented progress bar [XX__] Which I think are all slightly better than the magic text that appears when you've added your forth: "A maximum of four layouts are supported."
> if you need to present such text something is wrong either in the code or in the presentation. Even worse - something is wrong in the architecture:) > segmented progress bar [XX__] Actually, the progress bar looks like an interesting (and visually clear) representation. Is it HIG-compliant?
*** Bug 646269 has been marked as a duplicate of this bug. ***
This is fixed in 3.6
At least in Unity the bug is not fixed and the problem remains
(In reply to comment #10) > At least in Unity the bug is not fixed and the problem remains Unity doesn't use the input sources from GNOME.