ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
garnacho has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
garnacho has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
guru_ has quit [Ping timeout: 480 seconds]
guru_ has joined #wayland
guru__ has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
guru_ has joined #wayland
Guru_DE has joined #wayland
guru__ has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
guru_ has joined #wayland
Calandracas has quit [Quit: Leaving]
Calandracas has joined #wayland
Guru_DE has quit [Ping timeout: 480 seconds]
guru__ has quit [Ping timeout: 480 seconds]
guru__ has joined #wayland
Company has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
guru_ has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
Company has joined #wayland
guru_ has joined #wayland
guru__ has quit [Ping timeout: 480 seconds]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
Company has quit [Remote host closed the connection]
Calandracas_ has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
Company has joined #wayland
Calandracas has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
guru__ has joined #wayland
guru_ has quit [Ping timeout: 480 seconds]
guru_ has joined #wayland
bjorkint0sh has joined #wayland
guru__ has quit [Ping timeout: 480 seconds]
bjork1intosh has quit [Ping timeout: 480 seconds]
nerdopolis has quit [Ping timeout: 480 seconds]
mxz_ has joined #wayland
Guest2258 has quit [Ping timeout: 480 seconds]
mxz has quit [Ping timeout: 480 seconds]
mxz_ is now known as mxz
feaneron has quit [Ping timeout: 480 seconds]
Company has quit [Quit: Leaving]
glennk has quit [Ping timeout: 480 seconds]
iconoclasthero_ has joined #wayland
iconoclasthero has quit [Ping timeout: 480 seconds]
mxz_ has joined #wayland
paulk has quit [Ping timeout: 480 seconds]
paulk has joined #wayland
coldfeet has joined #wayland
coldfeet has quit [Remote host closed the connection]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
klausvalka has joined #wayland
klausvalka has quit [Remote host closed the connection]
mripard has joined #wayland
coldfeet has joined #wayland
<karenw>
So, on my copy of wayland-protocols. Cursor Shape (staging) depends on tablet v2 (unstable). That seems... weird?
<karenw>
I would assume that something in staging can't depend on unstable, and anything in stable can't depend on something in staging/unstable?
<whot>
karenw: the tablet protocol has been declared stable in one of the last releases
kts has joined #wayland
<karenw>
Why I said 'on my copy' it is the correct way round on wayland.app.
sima has joined #wayland
<karenw>
Is Cursor Shape intended to eventually replace .set_cursor() for most applications? Or purely an optional extra? (My question is mainly for desktop compositors)
tzimmermann has joined #wayland
kts has quit [Quit: Konversation terminated!]
<colinmarc>
karenw: games will probably always set custom cursors, I think
kts has joined #wayland
<karenw>
The way the core protocol is structured it's impossible for a compositor not to support it. I was more thinking of applications that only use common/theme cursors.
<karenw>
Regardless, for the foreseeable future I need to support both.
coldfeet has quit [Remote host closed the connection]
privacy has joined #wayland
FreeFull has quit [Ping timeout: 480 seconds]
Sachiel_ has joined #wayland
Sachiel has quit [Ping timeout: 480 seconds]
<jadahl>
karenw: think of it more as an optimization, unless your client only intends to support a specific compositor version.
<jadahl>
an opportunistic optimization, that is
glennk has joined #wayland
Sachiel_ is now known as Sachiel
kts has quit [Ping timeout: 480 seconds]
bjork1intosh has joined #wayland
bjorkint0sh has quit [Ping timeout: 480 seconds]
karenw has quit [Ping timeout: 480 seconds]
<MrCooper>
benh: you only need to worry about conflicts, a straightforward rebase can easily be done as part of merging
<MrCooper>
benh: gitlab should send you an e-mail notification when your MR conflicts with main
<benh>
okj
<benh>
MrCooper: yeah it did yesterday (conflict with the CI file of course) so I rebased... I suppose now I just wait for somebody to pick it up ?
<MrCooper>
probably, yeah
rasterman has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
garnacho has joined #wayland
kts has quit [Read error: Connection reset by peer]
mvlad has joined #wayland
Vanfanel has joined #wayland
<Vanfanel>
Hello. When building libwayland manually and installing it, there's no .cmake file generated/installed, so doing something like "find_package(Wayland)" fails.
<Vanfanel>
Is there a way to get the .cmake file generated by the Meson build system for Wayland? Or is pkg_check_modules() the usual way to use CMake in projects linking against libwayland?
<karenw>
TIL my code doesn't run on sway. `xdg_surface@11: error 3: xdg_surface has never been configured`
<karenw>
I tried injecting a display_roundtrip after creating the window before first attaching a buffer/commiting but I still don't get a configure?
jkl has quit [Quit: Gone.]
<zamundaaa[m]>
karenw: you need to actually wait with the first buffer until you get the configure, not just do a roundtrip
<karenw>
zamundaaa[m]: So... that could be indefiite? My code currently assumes once I've made the wl_surface and xdg_toplevel that I can just hand everything over to vulkan.
jkl has joined #wayland
<zamundaaa[m]>
karenw: if the compositor *never* sends the configure event, that would be a bug
<zamundaaa[m]>
In general though, unless the protocol text for an event has specific guarantees about when it'll be sent, you can't make assumptions about it
<karenw>
Yeah I never seem to get a configure if I just sit in a poll event loop forever. I'm missing something but I don't know what.
karenw has quit [Remote host closed the connection]
karenw has joined #wayland
<karenw>
(I disconnected there if anyone replied to me)
<karenw>
Ah, I need to do a wl_commit before attaching the first buffer
<karenw>
*wl_surface_commit
garnacho has joined #wayland
bodiccea_ has quit [Remote host closed the connection]