ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
Brainium has quit [Quit: Konversation terminated!]
Moprius has quit [Remote host closed the connection]
nerdopolis has quit [Ping timeout: 480 seconds]
mclasen has quit [Ping timeout: 480 seconds]
glennk has quit [Ping timeout: 480 seconds]
jkl has quit [Ping timeout: 480 seconds]
jkl has joined #wayland
bodiccea_ has quit [Ping timeout: 480 seconds]
kts has joined #wayland
tzimmermann has joined #wayland
<riteo>
Hi, I can see that destructor methods are declared as such in the XML. Is there a way of detecting this tag in the files generated by wayland-scanner?
banghe has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
<riteo>
nvm I think. Basically I'm kinda unsure on what to do with "server-side" ids. I'm not really sure how to free them from the proxy, if I even should.
<ifreund>
(this info should really be in the main wayland docs)
<ifreund>
the question of when to destroy server-side ids depends a lot on the protocol
<banghe>
The wayland is essentially only about input handling and buffer management. So why Does Wayland involved with Seat? I don't understand.
<riteo>
thank you ifreund!
<vyivel>
banghe: that's a part of input handling
rasterman has joined #wayland
flokli has quit [Quit: WeeChat 4.5.1]
coldfeet has quit [Quit: Lost terminal]
flokli has joined #wayland
vincejv has joined #wayland
sima has joined #wayland
kts has quit [Ping timeout: 480 seconds]
funderscore is now known as f_
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
sima has quit [Ping timeout: 480 seconds]
iomari891 has joined #wayland
mclasen has joined #wayland
sima has joined #wayland
narodnik has quit [Quit: WeeChat 4.5.2]
kts has joined #wayland
narodnik has joined #wayland
mvlad has joined #wayland
feaneron has joined #wayland
<MrCooper>
AFAICT the xdg_popup "topmost" concept is purely about creation/destruction of the popup object, whether or not the popup is currently mapped doesn't matter, does it?
mclasen has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
banghe has quit [Remote host closed the connection]
mclasen has joined #wayland
mclasen has quit [Quit: mclasen]
iomari891 has quit [Ping timeout: 480 seconds]
Moprius has joined #wayland
zzxyb[m] has joined #wayland
<zzxyb[m]>
Is there any way to reduce the number of eglCreateImageKHR and eglDestroyImageKHR calls for the wl_drm protocol in the Wayland compositor?
<kennylevinsen>
hmm? what's still using the deprecated wl_drm protocol?
<zamundaaa[m]>
zzxyb: yes, just don't use wl_drm at all
<zamundaaa[m]>
100% optimization with this simple trick!
<kennylevinsen>
A+, cured all ailments, would buy again
akimoto has joined #wayland
<zzxyb[m]>
<zamundaaa[m]> "zzxyb: yes, just don't use..." <- 😀
rgallaispou has joined #wayland
nerdopolis has joined #wayland
narodnik has quit [Quit: WeeChat 4.5.2]
narodnik has joined #wayland
kts has joined #wayland
<MrCooper>
zzxyb[m]: do you mean not calling eglCreateImageKHR every time the same buffer is attached to a surface?
akimoto has quit [Remote host closed the connection]
kts has quit [Ping timeout: 480 seconds]
narodnik has quit [Quit: WeeChat 4.5.2]
lsd|2 has joined #wayland
lsd|2 has quit []
cwittlut has quit [Ping timeout: 480 seconds]
narodnik has joined #wayland
<MrCooper>
the xdg_wm_base not_the_topmost_popup error description says "the client tried to map or destroy a non-topmost popup", should that say "tried to unmap"?
* kennylevinsen
vaguely remembers making an issue about this some time back
<MrCooper>
looks only loosely related, my questions are specifically about whether or not (un)mappedness matters for the "topmost" concept
<kennylevinsen>
The main phrase that is strict about it is:
<kennylevinsen>
> Nested popups must be destroyed in the reverse order they were created in, e.g. the only popup you are allowed to destroy at all times is the topmost one.
<kennylevinsen>
this effectively defines the order to be creation order
<kennylevinsen>
it's presumably still legal to unmap the surface, but destruction order is strict
<kennylevinsen>
(which I find a bit silly)
<kennylevinsen>
that MR also mentions that the wording originates from grabs
<MrCooper>
FWIW, mutter sends that error when the parent surface is unmapped
<MrCooper>
before the popup
<riteo>
yea I think that's the most common interpretation actually
<riteo>
I /think/ I've seen this behavior across all major compositors
<riteo>
been a while since I messed around real hard with popups though
<riteo>
oh wait I misread sorry
<riteo>
I mean like, unmapping still causes that error
<riteo>
no yea I think MrCooper meant that
<MrCooper>
yep, the spec doesn't really seem to say that yet though
mclasen has quit [Ping timeout: 480 seconds]
mohit815822635306 has quit [Quit: mohit815822635306]
mohit815822635306 has joined #wayland
Brainium has joined #wayland
iomari891 has joined #wayland
<MrCooper>
mvlad: AFAICT weston sends an XDG_SURFACE_ERROR_DEFUNCT_ROLE_OBJECT error only if the client tries to do something with the role object after destroying the xdg_surface object, the spec says it should be sent when destroying the latter though
<MrCooper>
(mutter currently never sends that error AFAICT)
mclasen has joined #wayland
mclasen has quit []
mclasen has joined #wayland
<MrCooper>
AFAICT mutter / kwin / weston never send a WL_SURFACE_ERROR_DEFUNCT_ROLE_OBJECT error, wonder what would break if that's fixed
<vyivel>
wlroots enforces it and it works fine
nerdopolis has quit [Read error: Connection reset by peer]
AJ_Z0 has quit [Quit: I have to return some videotapes]
tzimmermann has quit [Quit: Leaving]
AJ_Z0 has joined #wayland
mclasen has quit [Quit: mclasen]
<riteo>
yay the proxy multiplexer thing I did seems to finally have reached a "good enough" status! I can multiplex two godot instances (admittedly with just the base protocols enabled) and can close and open the "secondary" clients fine!
<riteo>
Stuff seems to not (visibly) leak, at least when it comes to ids.
<riteo>
I don't want to celebrate victory too soon but I think that it's quite safe to say at this point that the proxy approach is indeed feasible!
<riteo>
I'll try to redirect a window to a subsurface _somehow_ (there are a few ways that come to mind) soon
garnacho has quit [Ping timeout: 480 seconds]
garnacho has joined #wayland
kenny has quit [Ping timeout: 480 seconds]
feaneron_ has joined #wayland
feaneron has quit [Ping timeout: 480 seconds]
mahkoh has joined #wayland
feaneron_ has quit []
feaneron has joined #wayland
feaneron has quit [Remote host closed the connection]
feaneron has joined #wayland
<mahkoh>
Is it fixed API that `wl_proxy_get_listener` returns the dispatcher user data if a dispatcher was set on a wl_proxy?