Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shortcuts broken on language change #1986

Closed
RuRo opened this issue Dec 3, 2021 · 2 comments
Closed

Shortcuts broken on language change #1986

RuRo opened this issue Dec 3, 2021 · 2 comments

Comments

@RuRo
Copy link
Contributor

RuRo commented Dec 3, 2021

I've just updated from 3.7.0 to 3.8.1 and the update partially broke shortcuts for me.

Describe the bug

A bit of context first: I use 2 languages - English and Russian. The keyboard layout is a mostly standard en-US layout, but the letter keys also have Russian letters printed on them. You can switch between the Russian and English "layouts" on the fly. Here's an image:

image

The tricky part is that shortcuts should ignore, which language is selected and should instead respond to the physical keys that are being pressed. For example, if I configure Shift+Ctrl+Q to the New tab action, then pressing the Shift, Control and Q keys together should open a new tab even if I have the Russian language enabled. Note, that with a Russian layout enabled, pressing the physical Q key would normally "type" the letter Й.

To be clear, this is not a feature request. The behaviour I am describing is the "default" and 99.9% programs with shortcuts work that way. Guake version 3.7.0 handles the shortcuts correctly, so this is a regression.

Expected behavior

Keyboard shortcuts should ignore, which keyboard language is currently selected.

Actual behavior

The shortcuts are language specific.


$ guake --support

Guake Version: 3.8.1

Vte Version: 0.66.1

Vte Runtime Version: 0.66.1


GTK+ Version: 3.24.30

GDK Backend: <GdkX11.X11Display


Desktop Session: plasma


Display: :0

RGBA visual: True

Composited: True

  • Monitor: 0 - CMN eDP-1
    • Geometry: 1920 x 1080 at 1920, 0
    • Size: 382 x 215 mm²
    • Primary: True
    • Refresh rate: 60.002 Hz
    • Subpixel layout: unknown
  • Monitor: 1 - ACI HDMI-2
    • Geometry: 1920 x 1080 at 0, 0
    • Size: 528 x 310 mm²
    • Primary: False
    • Refresh rate: 60.0 Hz
    • Subpixel layout: unknown
@Davidy22
Copy link
Collaborator

Davidy22 commented Dec 4, 2021

Oh, we have #1953 merged in master slated for 3.8.2 already that should deal with this, I wanted to fix a deployment to pypi issue before signing off the release but it's taken a while. I'll take another run at it again, maybe I'll just skip pypi again for 3.8.2 if I still can't get the pypi build to work.

@RuRo
Copy link
Contributor Author

RuRo commented Feb 15, 2022

I updated to 3.8.5 and so far the issue seems to be fixed, so I am closing this for now. Thanks!

@RuRo RuRo closed this as completed Feb 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants