After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 696271 - Complicated setting of keyboard layout
Complicated setting of keyboard layout
Status: RESOLVED OBSOLETE
Product: gnome-control-center
Classification: Core
Component: Region & Language
3.7.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2013-03-21 11:06 UTC by Lukas Zachar
Modified: 2021-06-09 16:25 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Removed the page where the more symbolic icon comes up. Window is given a minimum size requirement it is supossed to follow. A forward arrow is given for indicating there is a submenu. (7.65 KB, patch)
2017-07-19 10:51 UTC, Chris
none Details | Review

Description Lukas Zachar 2013-03-21 11:06:52 UTC
When I was setting regional keyboard layout I felt it wasn't as straightforward as it could be. I was looking for slovak/czech layout, which is not in the top languages listed.

a) I prefer text to the graphical representation of 'more'. Although there is a mouse hint and a position of the icon is a kind of hint too.

b) It is not possible to search for the language by typing until 'more' is clicked. I thing it should be consistent with 'activities' e.g. start typing and the search box is opened immediately.

c) The way to order layouts is missing (or I am not able to find it).
Comment 1 Rui Matos 2013-03-21 11:54:24 UTC
(In reply to comment #0)
> a) I prefer text to the graphical representation of 'more'. Although there is a
> mouse hint and a position of the icon is a kind of hint too.

This is as designed, see bug 694927.

> b) It is not possible to search for the language by typing until 'more' is
> clicked. I thing it should be consistent with 'activities' e.g. start typing
> and the search box is opened immediately.

I think we can this, Allan what do you think?

> c) The way to order layouts is missing (or I am not able to find it).

We're not doing this since the input source switcher now re-orders the sources in MRU (most recently used) order. Given that, do you still feel the need to manually define an order?
Comment 2 Lukas Zachar 2013-03-21 17:39:56 UTC
Thanks for the explanation.

(In reply to comment #1)
> > c) The way to order layouts is missing (or I am not able to find it).
> 
> We're not doing this since the input source switcher now re-orders the sources
> in MRU (most recently used) order. Given that, do you still feel the need to
> manually define an order?

I would still prefer to order it manually. 
What will happened if there are more then 2 layouts? E.g.:
1. Layouts A, B, C in that order
2. Use B
3. Layouts are now B, A, C or B, C, A 

I think that will be a fight against muscle memory if each layout is used often enough as you will find them ordered differently every time.
Comment 3 Allan Day 2013-03-21 17:58:42 UTC
(In reply to comment #1)
> > b) It is not possible to search for the language by typing until 'more' is
> > clicked. I thing it should be consistent with 'activities' e.g. start typing
> > and the search box is opened immediately.
> 
> I think we can this, Allan what do you think?

It's a balance between making the common stuff easy to find. There's undoubtedly a negative side effect if your language is not in the initial short list, but I think it's a good trade off on the whole. After all, adding input sources isn't something that people do all that often.

One thing we could try is having typing trigger the search box, like we do elsewhere in GNOME 3.
Comment 4 Allan Day 2013-03-21 17:59:46 UTC
(In reply to comment #2)
> I would still prefer to order it manually. 
> What will happened if there are more then 2 layouts? E.g.:
> 1. Layouts A, B, C in that order
> 2. Use B
> 3. Layouts are now B, A, C or B, C, A 
> 
> I think that will be a fight against muscle memory if each layout is used often
> enough as you will find them ordered differently every time.

Could you give us some feedback after you have used it for a while?

This is exactly the same as for switching applications, and has the advantage of making it easier to switch between two layouts.
Comment 5 Bastien Nocera 2013-04-22 09:31:07 UTC
Waiting on feedback.
Comment 6 Lukas Zachar 2013-04-22 19:29:13 UTC
Hi, I'm sorry to make you waiting.
I'll be glad to provide the feedback, however I need much more time as Gnome 3.8 is not yet available on stable Fedora. 
I plan to start using it sometime before beta. That said the ETA for the feedback is around mid June.
Comment 7 Lukas Zachar 2013-06-11 15:22:05 UTC
Hi, here is what I think after using it for some time.

I have 3 keyboard layouts - EN, SK, CS. 
Majority of time I use EN, time-to-time SK and sporadically CS.
I set this order of layouts each time, so my muscle memory is very strong here.

My typical use case is: 
1. typing in EN
2. realize I need something in SK
3. then something in CS
4. finally back to EN

In the past it was (No is the state, <switch> means to press keyboard shortcut to switch layout): 1. <switch> 2. <switch> 3. <switch> 4. 
If I wanted CS directly: 1. <switch> <switch> 3. <switch> 4.

With the new behavior it become: 1. <switch> 2. <switch> <switch> 3. <switch> <switch> 4. BUT for the order has changed to EN-CS-SK.

The only problem I have here is that now I have to read the notification to see what is the current order of layouts. And that disturbs me ;) 

But I agree that for two layouts, e.g EN-SK-EN, it is much better. But if you mix between that some 3rd (or more) layout it gets problematic.
Comment 8 Chris 2017-07-19 10:51:30 UTC
Created attachment 355931 [details] [review]
Removed the page where the more symbolic icon comes up. Window is given a minimum size requirement it is supossed to follow. A forward arrow is given for indicating there is a submenu.
Comment 9 André Klapper 2021-06-09 16:25:13 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new bug report at
  https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/

Thank you for your understanding and your help.