ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Moprius has joined #wayland
Narrat has quit []
garnacho has quit [Ping timeout: 480 seconds]
Moprius has quit [Quit: bye]
Brainium has quit [Quit: Konversation terminated!]
lsd|2 has quit [Ping timeout: 480 seconds]
fmuellner has quit [Ping timeout: 480 seconds]
feaneron has quit [Quit: feaneron]
glennk has quit [Ping timeout: 480 seconds]
yaslam has quit [Read error: No route to host]
yaslam has joined #wayland
thrice has joined #wayland
yaslam_ has joined #wayland
yaslam has quit [Ping timeout: 480 seconds]
yaslam_ has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
yaslam has joined #wayland
m5zs7k has quit [Ping timeout: 480 seconds]
yaslam_ has joined #wayland
yaslam has quit [Read error: Connection reset by peer]
yaslam has joined #wayland
m5zs7k has joined #wayland
yaslam_ has quit [Read error: Connection reset by peer]
yaslam has quit [Remote host closed the connection]
nerdopolis has quit [Ping timeout: 480 seconds]
m5zs7k has quit [Ping timeout: 480 seconds]
m5zs7k has joined #wayland
kts has joined #wayland
yaslam has joined #wayland
bodiccea_ has quit [Ping timeout: 480 seconds]
kts has quit [Quit: Leaving]
karenw has quit [Ping timeout: 480 seconds]
pavlushka has joined #wayland
diego2 has left #wayland [WeeChat 4.5.1]
dviola has joined #wayland
mohit815822635306 has quit [Ping timeout: 480 seconds]
mohit815822635306 has joined #wayland
naemi has quit [Quit: bye]
naemi has joined #wayland
pavlushka has quit [Ping timeout: 480 seconds]
JakeSays1 has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
pavlushka has joined #wayland
glennk has joined #wayland
tzimmermann has joined #wayland
rgallaispou has joined #wayland
rgallaispou has quit [Ping timeout: 480 seconds]
grinja has quit [Remote host closed the connection]
grinja has joined #wayland
sima has joined #wayland
<pq> emersion, the long threads in Mastodon between me and Troy for the past week or so are about tone mapping. I guess the main take-away is that a tone mapping algorithm is still an open research question.
bodiccea has joined #wayland
CME has quit []
bbhtt has quit [Quit: Bye!]
CME has joined #wayland
Plagman has quit [Remote host closed the connection]
bbhtt has joined #wayland
Plagman has joined #wayland
rasterman has joined #wayland
<emersion> aha, that's what I feared
<pq> Tony Vladusich raised a good point: https://mathstodon.xyz/@TonyVladusich/113935668726882902
<pq> my interpretation is that when down-mapping dynamic range, at some point when that range compression increases the picture becomes unnatural if you try to keep all details.
<pq> I think that's the problem of "HDR photos" mapped to SDR present in some camera apps.
iomari891 has joined #wayland
feaneron has joined #wayland
aspschn has joined #wayland
lsd|2 has joined #wayland
yaslam has quit [Read error: Connection reset by peer]
yaslam has joined #wayland
lsd|2 has quit []
rgallaispou1 has joined #wayland
aspschn has quit [Remote host closed the connection]
rgallaispou2 has quit [Read error: Connection reset by peer]
ecloud has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
JakeSays has joined #wayland
ecloud has joined #wayland
JakeSays1 has quit [Ping timeout: 480 seconds]
<JEEB> pq: yea, tone mapping is the thing that is very much not specified and everyone has their own special sauce
MrCooper_ has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
Moprius has joined #wayland
<wlb> weston Merge request !1682 opened by Robert Mader (rmader) Draft: libweston: Implement color-representation protocol https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/1682
thrice has left #wayland [WeeChat 4.0.4]
yaslam has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
yaslam has joined #wayland
pavlushka has quit [Ping timeout: 480 seconds]
mvlad has joined #wayland
pavlushka has joined #wayland
nerdopolis has joined #wayland
fmuellner has joined #wayland
<soreau> for something a bit less wild-west: github.com/soreau/wl-backdrop (wl-shm time/weather widget applet thingie)
saumon has quit [Ping timeout: 480 seconds]
saumon has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
bnason2 has joined #wayland
nerdopolis has joined #wayland
MrCooper_ is now known as MrCooper
dviola has quit [Quit: WeeChat 4.5.1]
bodiccea has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
agd5f_ has quit [Remote host closed the connection]
rgallaispou1 has quit [Read error: Connection reset by peer]
agd5f has joined #wayland
grinja1 has joined #wayland
grinja has quit [Ping timeout: 480 seconds]
d42 has joined #wayland
Moprius has quit [Quit: bye]
rgallaispou has joined #wayland
<zzag> emersion: is it okay with wlroots to reuse buffer storage after destroying a wl_buffer? https://gitlab.freedesktop.org/wayland/wayland/-/merge_requests/447
<zzag> speaking for kwin, it won't be
<zzag> because kwin can upload data from a shm buffer to a texture later
<zzag> so we expect the client not to touch the backing storage
<zzag> I believe wlroots and kwin handle buffers in a similar fashion
<zzag> I've been thinking about suggesting that the client is not allowed to reuse buffer storage if it destroys a buffer before receiving a release event
<daniels> that's the only possible answer
<vyivel> yeah i think that's how it always meant to be
<daniels> it's not just delayed SHM uploads, but there could also be delayed GPU work (even if it's flushed, it's not guaranteed to have finished), overlays, etc etc
<zzag> okay, cool!
Brainium has joined #wayland
<zzag> "I've been thinking about suggesting that the client is not allowed to reuse buffer storage if it destroys a buffer before receiving a release event" ah, wl_surface.attach documentation already covers it \o/
kts has joined #wayland
Calandracas has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
coldfeet has joined #wayland
tzimmermann has quit [Quit: Leaving]
iomari891 has joined #wayland
kts has quit [Quit: Leaving]
agd5f_ has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
<emersion> zzxyb[m]: client can release, but not reuse
<emersion> er
<emersion> zzag: ^
agd5f has quit [Ping timeout: 480 seconds]
<emersion> release the backing storage, i mean
<emersion> e.g. on shutdown
<emersion> or when re-allocating a swapchain
<emersion> since the compositor still has a ref to the backing storage via mmap, the OS will not re-use that memory again for a new alloc until the compositor unmaps it
pavlushka has quit [Ping timeout: 480 seconds]
coldfeet has quit [Quit: Lost terminal]
pavlushka has joined #wayland
agd5f has joined #wayland
agd5f_ has quit [Ping timeout: 480 seconds]
<DemiMarie> emersion: can you look at my MR for libwayland to fix the infinite loop?
Calandracas has joined #wayland
linyaa has joined #wayland
<linyaa> hi, i'm searching for the latest in-progress protocol work for VK_EXT_present_timing.
<linyaa> can someone point me to the latest MRs or protocol?
<linyaa> sorry, i'm not skilled at navigating wayland development.
iomari891 has joined #wayland
bodiccea has joined #wayland
Moprius has joined #wayland
sewn has quit [Ping timeout: 480 seconds]
iomari891 has quit [Ping timeout: 480 seconds]
rasterman has quit [Quit: Gettin' stinky!]
ezzieyguywuf has joined #wayland
<ezzieyguywuf> is there a way to request from the server what size it thinks my window should be? or do I have to specify a prefered default width/height?
narodnik has joined #wayland
camaro_owner has joined #wayland
camaro_owner has left #wayland [#wayland]
<vyivel> ezzieyguywuf: the server will tell you either way in xdg_toplevel.configure
<vyivel> unless the size is 0,0 in which case pick something sensible on your own
yrlf has quit [Ping timeout: 480 seconds]
yrlf has joined #wayland
pavlushka has quit [Ping timeout: 480 seconds]
mvlad has quit [Remote host closed the connection]
Markiplier has joined #wayland
<Markiplier> hello?
Moprius has quit [Quit: bye]
<Markiplier> are you all just daemons?
FreeFull has quit []
grinja2 has joined #wayland
grinja1 has quit [Remote host closed the connection]
<DemiMarie> Markiplier: why do you ask?
<DemiMarie> did you hear something negative about Wayland?
feaneron has quit [Ping timeout: 480 seconds]
<Markiplier> erm no
<Markiplier> there's little activity here
sima has quit [Ping timeout: 480 seconds]
Markiplier has left #wayland [#wayland]
<bl4ckb0ne> its late
<ezzieyguywuf> vyivel: it's telling me 0 width and 0 height lol
<ezzieyguywuf> unless I'm doing something w rong
bodiccea has quit [Ping timeout: 480 seconds]
<ezzieyguywuf> e.g. this is the log I'm currently dumping: Got CONFIGURE for xdg_toplevel, xdg_shell_client.Toplevel.Event__struct_3355{ .width = 0, .height = 0, .states = common.Array{ .size = 0, .alloc = 0, .data = anyopaque@9aa5f5c } }
<soreau> ezzieyguywuf: vyivel mentioned that you can choose your own size if the configure event size is 0x0
<ezzieyguywuf> ahh I missed that
any1 has quit [Ping timeout: 480 seconds]
<ezzieyguywuf> so 0,0 is a valid response from the server - is there a way for me to coerce the server into giving me a value? e.g. on sway (which I'm using right now), I don't understand what it means for a window to be 0,0, since there's no concept of "minimize"
<ezzieyguywuf> ah, ok so if I go ahead and set my own width/height, I get _another_ event (after 0,0), where sway tries to set the window to its desired dimensions
narodnik2 has joined #wayland
<ezzieyguywuf> I find that odd though I wish it would just tell me from the rip what size it wants, I hate to guess at an "appropriate" size, especially for non-tiling compositors
Markiplier has joined #wayland
Markiplier has left #wayland [#wayland]
narodnik2 has quit [Ping timeout: 480 seconds]