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

wayland client with native bindings #2368

Open
totaam opened this issue Jul 25, 2019 · 5 comments
Open

wayland client with native bindings #2368

totaam opened this issue Jul 25, 2019 · 5 comments
Milestone

Comments

@totaam
Copy link
Collaborator

totaam commented Jul 25, 2019

Following up #2243, we will need some form of native bindings to:

  • query the keyboard layout
  • access the clipboard
    etc..
@totaam
Copy link
Collaborator Author

totaam commented Jul 25, 2019

According to libxkbcommon quick guide: If we are a Wayland client, the compositor gives us a string complete with a keymap.
Not sure where, no attributes in the GTK.EventKey, or in its GdkWaylandDevice attribute..

More keyboard related tickets: #1049, #856

@totaam
Copy link
Collaborator Author

totaam commented Jul 25, 2019

2019-07-25 15:48:47: mviereck commented


Keyboard:
On systems with systemd the output of localectl status might be a good guess.
The Wayland compositor might still be configured different, but I assume most systems will have the same keyboard configuration on tty as on the desktop.
On my german system I get the same valid output on tty, in X and in Wayland:

$ localectl status
   System Locale: LANG=de_DE.UTF-8
       VC Keymap: n/a
      X11 Layout: de
       X11 Model: pc105

@totaam
Copy link
Collaborator Author

totaam commented Jul 28, 2019

On systems with systemd the output of localectl status might be a good guess.

Thanks, added this as fallback in r23321.

@totaam
Copy link
Collaborator Author

totaam commented Sep 13, 2022

So many things won't work as well under wayland...
#3614 (comment)

@totaam
Copy link
Collaborator Author

totaam commented Dec 2, 2024

Many years on, and things still don't work as well under Wayland as they do under X11.
(missing features, opinionated behaviour, etc)

I don't agree with all the points made here, but some have merit:
Wayland, where are we in 2024? Any good for being the default?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant