ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<MrCooper>
ManMower: "commit-timing-v1 doesn't provide a queue" it's not that simple; as emersion pointed out in https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/248#note_2116119 , even core Wayland has an implicit queue, since the client can attach any number of buffers before any of them become ready / are released by the compositor
mbalmer has joined #wayland
Guest2449 has quit [Remote host closed the connection]
zzoe-` has left #wayland [Glined: User has been banned from the network.]
<YaLTeR[m]>
damn oftc isn't safe either
<Nova[m]>
what happened here
<mupuf>
YaLTeR[m]: IRC as a whole isn't safe
<YaLTeR[m]>
spam looks similar to what we had on the leftovers of gimpnet a few days ago
<emersion>
mupuf: matrix is worse
<mupuf>
emersion: i can believe that! I prefer anyway ;)
<mupuf>
But yeah, read the room spammers
<mupuf>
You are wasting your time
<doras>
emersion: not my experience.
<emersion>
you are lucky then
pochu has joined #wayland
<ambasta[m]>
ugh, that MR for absolute positioning turned ugly so fast :D
<ambasta[m]>
Is it acceptable to provide comments on such proposals as a non-dev?
<bookworm>
not sure adding to the peanut gallery is particularly useful...
<ambasta[m]>
I see, will refrain. Thanks
lain_ has joined #wayland
junaid has joined #wayland
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
mblenc has joined #wayland
gusnan has quit [Read error: Connection reset by peer]
gusnan has joined #wayland
mblenc1 has joined #wayland
junaid has quit [Remote host closed the connection]
mblenc has quit [Ping timeout: 480 seconds]
privacy has joined #wayland
<kennylevinsen>
ambasta[m]: it is acceptable, but remember that it mainly brings value if you add something new to the discussion, rather than repeating opinions
<ambasta[m]>
Certainly, I was going to propose alternate solutions as a discussion point. But maybe some poc would be more useful to suggest an alternate approach
<ambasta[m]>
This is something that the wine wayland driver is also writing hacks around
<ambasta[m]>
And also, jetbrains
junaid has joined #wayland
<any1>
An alternative approach has already been submitted.
<any1>
Now, I wonder, my proposal for transient seats was accepted a while ago. What happens now?
Moprius has joined #wayland
nerdopolis has joined #wayland
Moprius has quit [Quit: bye]
<swick[m]>
ManMower: I'm not so sure that timing and queue can be separated...
<swick[m]>
but separating timing feedback from presentation timing is a good idea either way
AnuthaDev has joined #wayland
kts has joined #wayland
<soreau>
xwayland gets to position clients on wayfire..
* soreau
hides
neniagh has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
kts has quit [Ping timeout: 480 seconds]
AnuthaDev has quit []
AnuthaDev has joined #wayland
glennk has quit [Quit: Leaving]
glennk has joined #wayland
AnuthaDev has quit []
<ManMower>
MrCooper: fair enough - I suppose what I meant to say was that commit-timing-v1 in its current state doesn't allow clients to explicitly control a queue.
<ManMower>
swick[m]: not 100% sure myself. queue control without timestamps is mucky, perhaps completely useless. (vulkan must commit before returning from present, a client using vulkan may want to do commits of its own between those vulkan commits for whatever reason - having them queued on different refresh cycles craps up the framerate...)
junaid has quit [Remote host closed the connection]
junaid has joined #wayland
lain_ has quit [Ping timeout: 480 seconds]
lain_ has joined #wayland
Company has joined #wayland
privacy has quit [Quit: Leaving]
<Ermine>
Is mr for absolute positioning 247?
nerdopolis has quit [Ping timeout: 480 seconds]
<bl4ckb0ne>
yes
nerdopolis has joined #wayland
sevz has joined #wayland
AnuthaDev has joined #wayland
kts has joined #wayland
vyivel has quit [Remote host closed the connection]