Originally posted by Daktyl198
View Post
Announcement
Collapse
No announcement yet.
SDL2 Reverts Its Wayland Preference - Goes Back To X11 Default
Collapse
X
-
-
Originally posted by tildearrow View PostCouldn't the GNOME team just use a shader as a workaround? Night light is nothing more than lowering the blue and green channels...
Leave a comment:
-
Originally posted by caligula View PostMostly works? Webcam yes, screen share no. I guess you don't need that.
Leave a comment:
-
Originally posted by tildearrow View Post
Couldn't the GNOME team just use a shader as a workaround? Night light is nothing more than lowering the blue and green channels...
By using GAMMA_LUT, it just gives the display processor a CLUT that it can use to transform the image right before it gets sent out of the display connector.
Also it should be noted that this isn't just an Gnome issue. My understanding is that it KDE implements their blue-light rejection feature in the same way. Since GAMMA_LUT is a kernel-level feature, I'm pretty sure that Nvidia support for it would allow them to scrap the XRANDR method of changing the screen LUT that they use under Xorg and just use GAMMA_LUT for both sessions.
Leave a comment:
-
Originally posted by birdie View PostCountless things (for a start X11 has a single server, for Wayland we now have what? two dozens?) prove that whatever developers have on their minds is as remote from being rational and sensical as possible. If requiring common sense and much needed common API is trolling, then something might be wrong with someone's grey matter.
Sure there's a single X11 server, because that's the only implementation that stayed alive for 18 years among all the other efforts. The same could happen to Wayland where different implementations dwindle with time and everyone converges towards a single best effort. That's not an advantage of X11 nor a limitation of Wayland's design. There's no protocol in the world that mandates a single implementation that should be used by everyone. After all, protocols are made for interoperability. I fail to see how the Wayland communication protocol could force that.
Originally posted by birdie View PostSo please kindly never mention me again and never reply to my posts, OK?Last edited by Vermilion; 19 April 2022, 05:03 PM.
- Likes 4
Leave a comment:
-
Originally posted by birdie View Post
Countless things (for a start X11 has a single server, for Wayland we now have what? two dozens?)
I'm not sure that Wayland has anywhere near two dozen compositors but maybe I'm mistaken.
You should really watch Keith Packard's A Political History of X.
Originally posted by birdie View Post...prove that whatever developers have on their minds is as remote from being rational and sensical as possible.
If requiring common sense and much needed common API is trolling, then something might be wrong with someone's grey matter.
Originally posted by birdie View PostSo please kindly never mention me again and never reply to my posts, OK?
- Likes 5
Leave a comment:
-
Originally posted by birdie View PostSo please kindly never mention us again and never reply to our posts, OK?
I agree on many of your points, but your extremely toxic and aggressive attitude doesn't help.Last edited by tildearrow; 19 April 2022, 04:48 PM.
- Likes 3
Leave a comment:
-
Originally posted by Myownfriend View PostThe reason why Gnome night light doesn't work on Nvidia hardware in Wayland is because the driver doesn't support GAMMA_LUT
- Likes 1
Leave a comment:
-
Originally posted by Vermilion View Post
Was wondering how come the title mentioned Wayland yet you didn't link your issue sooner. Guess I needed more patience.
Countless people discussed that content with you for the past months, and how most of it doesn't make sense from a Display protocol's perspective. At this point I'm convinced you're just being a troll and a spammer.
So please kindly never mention me again and never reply to my posts, OK?
- Likes 1
Leave a comment:
-
Originally posted by Weasel View PostWhy does it matter if he codes? Design decisions that matter if you code are those internal to a project, not to an end user. If a design decision impacts end user then nobody gives a shit if he can code or not.
He believes, for example, that Wayland should have protocols built into it that enable a client to access the buffers of other clients and the compositor even though Wayland clients already have ways of doing that. Clients can do both of those things and more with Pipewire and it's done in a way that work for both Wayland and X11 sessions.
An end user would get the same result whether or not capture is done via Pipewire or via a Wayland or X11 extension, but birdie's pissed that it's not part of Wayland.
He's also argued that a shared object isn't actually a shared object if only one thing decides to use it. Dude just doesn't know what he's talking about.
Originally posted by Weasel View PostIn fact that's probably the issue here, since Wayland developers (those who develop the protocol I mean) are a bunch of retards who thinks the world revolves around their computing needs and reject any sensible feature request that other users want out of their display server/protocol because they use it on X11.
Claiming "it's not needed" makes them a bunch of lunatic fringe fucks.
Originally posted by Weasel View PostClaiming "it's not needed" makes them a bunch of lunatic fringe fucks.
- Likes 1
Leave a comment:
Leave a comment: