ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput | register your nick to speak
hardening has quit [Ping timeout: 480 seconds]
co1umbarius has joined #wayland
columbarius has quit [Ping timeout: 480 seconds]
V has quit [Remote host closed the connection]
V has joined #wayland
mcf_ has joined #wayland
mcf has quit [Read error: Connection reset by peer]
mcf_ has left #wayland [#wayland]
mcf has joined #wayland
rasterman has quit [Quit: Gettin' stinky!]
<ishitatsuyuki>
swick: I see, good to see an API that at least gives a hint to application which display is its primary display
<ishitatsuyuki>
Although I think that API should also exist for scale factors (now we're copying Mac again...)
<ishitatsuyuki>
> more specifically with scaling, you might be able to find a surface scale factor which works well for multiple outputs
<ishitatsuyuki>
I doubt this is a thing, assuming what you are talking about is taking the LCM of scale factors, that would be an enormous overhead (2x/3x becomes 6x for example) and probably not significantly better than just rescaling the 3x surface
<ishitatsuyuki>
In the existence of fractional scaling it's also not a good idea
naveenk2 has joined #wayland
leon-p has joined #wayland
leon-p_ has quit [Ping timeout: 480 seconds]
leon-p has quit []
naveenk2 has quit []
naveenk2 has joined #wayland
naveenk2 has left #wayland [#wayland]
AJC_Z0 has joined #wayland
AJ_Z0 has quit [Ping timeout: 480 seconds]
AJC_Z0 is now known as AJ_Z0
slattann has joined #wayland
tzimmermann has joined #wayland
slattann has quit []
dcz_ has joined #wayland
xexaxo has joined #wayland
slattann has joined #wayland
Lucretia has joined #wayland
xexaxo has quit [Ping timeout: 480 seconds]
xexaxo has joined #wayland
st3r4g has quit [Quit: おやすみ]
dcompoze has joined #wayland
dcompoze has quit []
slattann has quit []
dcompoze has joined #wayland
slattann has joined #wayland
go4godvin is now known as Guest4408
<emersion>
dottedmag: yes, compositors need to workaround the race
<pq>
staceee, any program that goes straing to libinput while using Wayland for anything is fundamentally broken. It cannot know which input devices to open, and it usually *can't* open them either.
Lucretia has quit [Remote host closed the connection]
Lucretia has joined #wayland
rasterman has joined #wayland
flacks has quit [Quit: Quitter]
flacks has joined #wayland
slattann has quit []
slattann has joined #wayland
slattann has quit []
<daniels>
wl_seat is also ... not the best interface
<swick>
ishitatsuyuki: if you have 1x and 2x scale outputs then rendering at 2x as long as the surface is visible on the 2x output at all makes sense for example
<ishitatsuyuki>
ok, you're right
xexaxo has quit [Ping timeout: 480 seconds]
<emersion>
i kind of wish there was just a wl_surface.suggested_scale event the compositor would send
<emersion>
and then the compositor decides the best value to send
Yggdrasil has joined #wayland
Yggdrasil has left #wayland [#wayland]
hardening has joined #wayland
xexaxo has joined #wayland
leon-p has joined #wayland
hendursa1 has quit []
hendursaga has joined #wayland
xexaxo has quit [Ping timeout: 480 seconds]
xexaxo has joined #wayland
leon-p has quit []
xexaxo has quit [Ping timeout: 480 seconds]
<ishitatsuyuki>
do you think a XSettings alternative is necessary for Wayland? Or should we just rely on GTKingdom ™?
<ebassi>
ishitatsuyuki: Considering the actual success of xsettings, I'm not entirely sure it'd be a good thing to replicate
<ishitatsuyuki>
replicate surely no, but unifying the GTK/KDE segmentation might make sense
<ishitatsuyuki>
given that GSettings is mostly feature complete and working fine it might be a matter of KDE adopting things or not
<ebassi>
Well, xsettings was created to bridge different settings storages, and yet it was never truly adopted outside of the GTK-based environments
<ebassi>
Hence my skepticism of a Round 2
<ebassi>
There's also the issue of KDE applications depending on a whole set of KDE components, including the control center, which makes using KDE apps under non-KDE environments harder or, at least, less palatable
<ebassi>
If you're not using GNOME, though, you can still configure GNOME-based apps and/or GTK-based ones
<ebassi>
Without necessarily installing GNOME components
<ebassi>
But I also guess that there's less of a case to be made to mix and match environments and applications, these days, unlike 20 years ago
<ishitatsuyuki>
very good arguments, I agree with you
<ebassi>
Don't want to put up stop energy, anyway; just speaking as a GTK dev that has been around the block for a while
xexaxo has joined #wayland
<swick>
ishitatsuyuki: fwiw I agree with emersion that a suggested scale event would likely be sufficient here
<ishitatsuyuki>
yeah that's fine
<ishitatsuyuki>
I hope there would be progress on fractional scaling though
<ishitatsuyuki>
but that's another topic
leon-p has joined #wayland
bodiccea has quit [Ping timeout: 480 seconds]
bodiccea has joined #wayland
xexaxo has quit [Ping timeout: 480 seconds]
rasterman has quit [Remote host closed the connection]
xexaxo has joined #wayland
dcompoze has quit []
kennylevinsen has left #wayland [#wayland]
kennylevinsen has joined #wayland
tzimmermann has quit [Ping timeout: 480 seconds]
quantum5 has quit []
quantum5 has joined #wayland
xexaxo has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
xexaxo has joined #wayland
rasterman has joined #wayland
cube1 has joined #wayland
danvet has quit [Ping timeout: 480 seconds]
pochu has joined #wayland
hardening has quit [Ping timeout: 480 seconds]
pochu has quit [Remote host closed the connection]