81–90 of 102 posts
Earlier quoted context omitted.
Protocol merges require compositor implementations to be ready ahead of merge.
They require two implementations. It's not going to help if these implementations are in the compositors nobody cares.
I was going to say something about it being 10 years now since Apple made high DPI screens mainstream. Windows still doesn't have it working 100% yet.
On the specific topic here, fractional scaling, macOS gets it disastrously wrong, only supporting downscaling, which means that it’s impossible to get pixel-perfect output on fractional scales, which are the norm on most of their devices. I seriously can’t comprehend how they ended up going that way, given that they were the ones in a position to force developers to get things right, far more than Windows, but no, th…
They did¹, but it turns out the simpler solution just works, and that pixel-perfect purity doesn't matter because your eyes can't resolve HiDPI pixels any more than they can resolve the grid of subpixels that they're made of.
Earlier quoted context omitted.
- screenshots work - the keyboard and mouse can be controlled programmatically, but unaware if xdotool itself works - I don't notice any input delay with the monitors at 60Hz - I'm using the unsupported GPU flag with SwayWM and 4k games and windowed games work for me - never tried disabling vsync. I'm guessing it won't work I suspect if you use fractional scaling, the games wont run at 4k, but instead the fraction of…
> I suspect if you use fractional scaling, the games wont run at 4k, but instead the fraction of 4k X11 games maybe; SDL's Wayland backend can deal with fractional scales and make it render at native 4k.
I still use X11, where and rely on the following features (amongst others): -taking screenshots -auto keyboard/mouse scripting with xdotool -not have unnecessary mouse/keyboard to monitor delay -4K fullscreen, windowed fullscreen and windowed gaming with nvidia drivers, for native and steam proton games -choosing to have vsync enabled or disabled in games -EDIT: I should another important one for me: xclip, read from…
People are responding to this comment by saying "Screenshots work," and yes, they do, somewhat. However, you're limited to using the screenshot tool built in to your Wayland compositor, rather than any third-party tool. For example, my favorite screenshot tool supports automatic timed screenshots, of particular windows or the whole screen or of a specified region, of one desktop or several, and various customizations…
That not true anymore... I use Flameshot
Earlier quoted context omitted.
Wayland is frame perfect, and it's great. What's the issue with allowing users or the compositor to disable that in really specific case without sacrificing the frame perfect principle for all other uses? It's the best of both worlds
With X11, you defaulted to having tearing but could run a compositor if you wanted in order to not have it. Then Wayland showed up and loudly proclaimed that that was unacceptable and we had to be pixel-perfect, every frame, every time. ...Then a few years later, Wayland added the ability to tear, because it turned out to be useful, bringing it back to parity with X. This isn't... necessarily... technically invalid,…
It was a good idea, but the implementation clearly isn't working.
My bet: Wayland will be the Windows Vista or the OS/2 of Linux.
Earlier quoted context omitted.
> I suspect if you use fractional scaling, the games wont run at 4k, but instead the fraction of 4k X11 games maybe; SDL's Wayland backend can deal with fractional scales and make it render at native 4k.
Sure, I'd expect anything Wayland native will work as expected. Are there many games with Wayland support though? Honest question.
Earlier quoted context omitted.
> For example, my favorite screenshot tool supports automatic timed screenshots, of particular windows or the whole screen or of a specified region, of one desktop or several, and various customizations. Those features aren't supported by my compositor, and I don't have a choice. So Wayland limits my options. Xorg doesn't support his either. Your screenshotting tool runs the timer and takes the screenshot when the ti…
You're missing my point. The Wayland architecture does not give me a choice in my screenshot, video recording, and remote desktop tool: you have to use the functionality built in to the compositor. Many compositors (notably GNOME and KDE) don't support the Wayland semi-standard interface for these things. You mentioned shotman, but that isn't even a real screnshotting tool: it's just a screenshot GUI that depends on…
Yes it does. Use the screenshot, screencast and remote desktop XDG portals for that. It's understandable you're confused because the X11 way was to try to jam everything into X extensions whether it made sense or not. The overall trend lately is to move APIs into other components (XDG portals, pipewire, DBus, systemd, etc.)
Earlier quoted context omitted.
> I still use X11, where and rely on the following features To which I would add: (1) taking screenshots from the command line (xwd) (2) moving windows around from the command line (xwit) (3) keyboard-free copy-paste between different programs: select to copy, middle-click to paste (4) global indicator of where my cursor is (xeyes) (5) define global key combinations that launch programs (xbindkeys) (6) globally confi…
See: https://news.ycombinator.com/item?id=32297479 None of these discussions ever go anywhere. They will tell you that wlroots is standardizing all these things etc etc but as it stands today every compositor is at best reimplementing a subset of the features you describe. If I had enough money I would pay the Wayland people to work on something else and let the project collapse because they are constantly underminin…
There is a way to protect against LD_PRELOAD: use sandboxing. X11 is bad for security because it's an intentional escape around the sandbox.
The "tear it down and build something else argument" is also going nowhere, anything else you build is going to run into the same questions of how to go about implementing these features.