It was not a pleasant journey, so to say. I don't remember which anymore, but a bit over a year ago, I tried switching everything to Wayland, and had too many problems in my specific hardware setup, went back to x11 and some things just broke and some apps I couldn't use. The best you can do is make your own wrappers to hide the fact you're calling unsafe code behind the scenes, but I can't see too much unnecessary unsafe code in there to be honest. Interacting with X11 requires tons of unsafe operations, you can't really work around that. The copious amount of unsafe seems to revolve around operating system APIs being called. A simple button to fix the problem can be a lot better than an error message with a link to a complicated step-by-step guide.Īs is often the case, this client seems to have been made for people running Ubuntu/Fedora, and a relatively recent version at that. When a piece of software says "You are using Wayland and this software requires X11, please change your desktop session type" then you're not helping most people. And, to be honest, I'm not 100% opposed to this approach, although there should definitely be a giant warning system configuration is changed. This tool was clearly written by someone with a "make it work for the general public" mindset. That said, the "let's disable Wayland to fix it" approach is very. Screen sharing is a possibility, but that's it: injecting key strokes or mouse input into applications can only be done by even worse hacks. I don't think the application can work on Wayland because it can't inject commands.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |