ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<DodoGTA>
ofourdan: The font path just says "built-ins" (so do I need some extra configuration or should I make an issue about the package?)
<DodoGTA>
Also is there a X11 equivalent of the WAYLAND_DEBUG variable?
<ofourdan>
DodoGTA: you can use xset at runtime or fix your build to add more fontpaths, e.g. a default fontpath where you'd add symlinks, that's what most distributions do.
guru__ has quit [Ping timeout: 480 seconds]
<ofourdan>
there is no equivalent to WAYLAND_DEBUG in X11, but there are tools (e.g. xscope)
<sewn>
is wl_surface::preferred_buffer_scale sent (initial scale) only after a surface has been drawn? or is it sent after surface creation?
<YaLTeR[m]>
the idea is to send it at surface creation whenever possible
Brainium has joined #wayland
<sewn>
it seems to be sent after the first initial commit
guru__ has joined #wayland
Guru_DE has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
<kchibisov>
sewn: it generally depends on the role.
guru__ has quit [Ping timeout: 480 seconds]
<kchibisov>
if you read a particular role surface docs it could mention when such state should be sent, for xdg-shell it should be before the first configure.
<kchibisov>
however for e.g. cursor surfaces/subsurfaces you can only send it after commit.
<kchibisov>
commit with buffer, I mean.
mclasen has joined #wayland
<mclasen>
swick[m]: you saw my comment on matrix about the typo in your mutter branch ?
rv1sr has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Calandracas_ has quit [Remote host closed the connection]
Calandracas_ has joined #wayland
linkmauve has joined #wayland
iconoclasthero has joined #wayland
<swick[m]>
mclasen: yup, just catching up on stuff
<mclasen>
do you plan switching your branch to v3 ?
<mclasen>
what even is the difference, and why add new features this late in the game?
<swick[m]>
I'm probably merging zamundaaa's changes today and release a v4 in the hope that no one started implementing v3 stuff yet
<swick[m]>
but yes, I'll update the mutter impl
* mclasen
would suggest to simple drop any features that don;t have a client-side implementation and call it good
<mclasen>
in interest of getting to the finish line
guru_ has joined #wayland
<swick[m]>
the v3/v4 stuff is kind of important for sdl, wine/proton
<zamundaaa[m]>
If the Mesa implementation adds scRGB support, we're already covering everything except set_primaries
<zamundaaa[m]>
And I can just make our image viewer support set_primaries
* mclasen
just a liiittle impatient at this point :)
Calandracas_ has quit []
<swick[m]>
I think we should be fine and getting a bit more real world testing before setting everything in stone is also not bad
Calandracas has joined #wayland
nerdopolis has joined #wayland
<mclasen>
swick[m]: whats the plan for getting that testing? are you going to merge the mutter branch ?
<mclasen>
its not getting testing while it sits in your mutter fork
Guru_DE has quit [Ping timeout: 480 seconds]
<swick[m]>
I'll try to get it merged soon, yes
<mclasen>
I can confirm that it works great for srgb :)
<swick[m]>
amazing :P
<mclasen>
once you do, gnome-nightly will start to be a tessting ground, with both client and compositor implementations