GNOME Bugzilla – Bug 346908
layout preview doesn't update on layout switching
Last modified: 2020-11-06 19:55:30 UTC
If I open the layout view, then switch keyboard layout, either using short-cuts, or by clicking on the keyboard indicator, the layout view doesn't update to the new layout.
I should not (at least it was never meant). It is not _current_ layout (is the a word "Current" in UI?), it is a layout which name is displayed on the top of the window. Redisplaying layout is a massive and slow task - is there real requirement for making it "realtime"?
When I press shift or ctrl, it highlights. That immediately suggests that if I use ctrl+shift to switch layout, it updates... Keep it as a feature request then.
It can cache the layout display of course.
Use case: I want to compare key placement between two layouts (e.g. to learn a phonetic layout's correspondence to English letters). Currently this requires opening a layout view, switching layout, opening another, maximizing both and Alt+Tabbing between them... This works quite well but it's not discoverable to beginners. And it requires a little more work. Use case 2: I want to learn my layouts while typing, so I'll keep a layout view window open [and always on top]. But when I switch layouts the view doesn't update, so now I have to open several of them and switch between them as I change layouts? Awkward! And finally, updating the display in real-time would be more consistent with Gnome's "changes are applied immediately" feel.
About performance: the Add Layout dialog shows layout previews in real time as the dropdowns are changed, and it reacts very quickly. So it shouldn't be such a problem.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old bug reports in Bugzilla which have not seen updates for many years. If you can still reproduce this issue in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/ Thank you for reporting this issue and we are sorry it could not be fixed.