-
Notifications
You must be signed in to change notification settings - Fork 118
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 status? #206
Comments
This is a very complex topic.
|
Thank you for the detailed reply!
Do you have an example of a compositor and a client where it's working like this today? When the candidate box will run as a Wayland client, I hope those of us who use a tiling window manager/compositor won't have trouble having it float. |
because sway doesn't implement the input_panel part in the protocol, actually I don't know any compositor implement that. (weston has zwp_input_method_v1 support, but no one use that except a broken weston-editor demo use text-input-v1.) Someone told me he implemented that in kwin and showed me a screen shot, but I didn't check if it's mainlined maybe it's under review or sth. Initially fcitx doesn't render anything at all if the input panel protocol is not available, because I think "what's point to workaround a broken one?" but people are asking me to render a X one as a fallback (#118), so I just add this support. Rendering a wayland one without input panel protocol is pointless because it can't do any positioning, using a X one at least it can do some "partial" position. If you want anything works the best, use gnome. It doesn't use zwp_input_method, instead, it is using ibus's dbus to communicate with input method server and text-input-v3 with client. As for gnome shell, it has a benefit that it has extension and have all window information + ability to position window, so kimpanel as an extension can try to position it correctly (for wayland client, it's "current window" + "offset" mode, for X11 it's absolution position mode). |
Let me put this as a reference here: #207 |
Thanks again! So Gnome is in the best shape if using the Kimpanel extension. It would be great if this info will be put somewhere visible. Maybe as a table?
|
I think you misunderstood, input_method_v2 popup is the candidate box for zwp_input_method_v2 |
zwp_input_method_v1 should be used with zwp_input_panel I didn't know about swaywm/sway#5890 when I looked at the last time, ideally with that sway may be able to show the window. There's also an alternative solution: ask application to draw the popup window, which I listed #207. |
Gedit and GNOME Terminal are native Wayland applications in Wayland session, while Firefox runs in XWayland without some configuration. For better integration between GNOME and Fcitx, you can try this extension: https://extensions.gnome.org/extension/261/kimpanel/ |
👍 thanks a loooot, this sovle the problem. |
Any chance for a clear overview of Wayland's support in and for Fcitx5? maybe a blog post or a roadmap?
The text was updated successfully, but these errors were encountered: