ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
paulk-bis has joined #wayland
Brainium has quit [Read error: Connection reset by peer]
paulk has quit [Ping timeout: 480 seconds]
fmuellner has quit [Remote host closed the connection]
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
lbia has quit [Remote host closed the connection]
DodoGTA has quit [Quit: DodoGTA]
tyzef has quit [Quit: WeeChat 4.1.1]
DodoGTA has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
tyzef has joined #wayland
jtbx has quit [Read error: Connection reset by peer]
jtbx has joined #wayland
leon-anavi has joined #wayland
Guest1747 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest1927
<Ermine>
Sorry for bringing this topic up again, but is there written-down reason for not supporting window placement in wayland?
<Ermine>
I guess I should read a discussion in the MR 247
mripard has joined #wayland
Leopold_ has quit [Remote host closed the connection]
<pq>
Ermine, Wayland in general targets things where there is no well-defined 2D coordinate system, and/or displays are not axis-aligned rectangles. Another reason is that a client cannot know of everything on the display, so it cannot make the best window positioning decisions.
<pq>
I'm not sure if such a write-up has been saved anywhere.
<pq>
Also the potential for window placement policy fighting between an app and a compositor.
DodoGTA has quit [Quit: DodoGTA]
<pq>
note, this is about global or per-output x,y coordinate based positioning. There are other ways to design positioning such that it doesn't clash with Wayland design principles that much.
<MrCooper>
pq: it's about the DRM_IOCTL_SYNCOBJ_EVENTFD ioctl, it allocates a struct eventfd_ctx which keeps the eventfd alive until it's signaled (or the syncobj is destroyed)
<pq>
MrCooper, why is close(2) not hooked up to release it?
<MrCooper>
I don't know of any mechanism for that
<pq>
how can a file description remain alive after the process has no fds referring to it anymore? It that normal?
<MrCooper>
actually I'm not sure offhand the eventfd file description itself stays alive, the eventfd_ctx does though
<pq>
Seems very strange to me. The UAPI side is intuitively obvious how to release them.
* emersion
doesn't really care about this stuff
<pq>
Are they accounted to the compositor process, or are they just generic kernel memory allocations not accounted to anyone like many things in DRM are AFAIU?
cmichael has joined #wayland
<pq>
I mean, all that compositors care about is to not exhaust their fd or memory quota. Anything else is the kernel's own problem.
<pq>
IOW, does it matter if the eventfd_ctx is not freed timely?
Guest1940 has quit [Remote host closed the connection]
iomari891 has joined #wayland
iomari891 has quit []
iomari891 has joined #wayland
tyzef has quit [Quit: WeeChat 4.1.1]
cool110 has joined #wayland
cool110 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest1956
<MrCooper>
AFAICT it doesn't
<MrCooper>
just trying to get to the bottom of that alluded issue
gusnan has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
mripard has joined #wayland
floof58 has quit [Quit: floof58]
floof58 has joined #wayland
gusnan has joined #wayland
fmuellner has joined #wayland
<dubiousness>
pq: do we know how 3D displays handle positioning? Things like VR headsets?
tyzef has joined #wayland
<dubiousness>
I’d imagine it’s a relational X,Y,Z coordinate system, though I must admit I haven’t looked into it
Leopold_ has joined #wayland
lsd|2 has joined #wayland
Leopold_ has quit [Remote host closed the connection]
<bl4ckb0ne>
dubiousness: for 2d clients in 3d space?
tyzef has quit [Quit: WeeChat 4.1.1]
tyzef has joined #wayland
<dubiousness>
bl4ckb0ne: yes
<bl4ckb0ne>
in wxrc i just let the compositor handle the Z axis and treat x and y as a big screen
<emersion>
but, each toplevel tree has its own 2d space
<bl4ckb0ne>
handle as in "theres a keybinding to bring the toplevel closer or further away"
<bl4ckb0ne>
yes, its just a plane
mclasen has joined #wayland
Guest1956 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest1966
Guest1966 has quit [Remote host closed the connection]
cool110_ has joined #wayland
cmichael has quit [Quit: Leaving]
cool110_ is now known as Guest1967
xyene_ has joined #wayland
xyene has quit [Read error: Connection reset by peer]
xyene_ is now known as xyene
sevz has quit [Quit: WeeChat 4.2.1]
sevz has joined #wayland
rv1sr has joined #wayland
mclasen_ has joined #wayland
mclasen_ has quit []
mclasen_ has joined #wayland
mclasen has quit [Ping timeout: 480 seconds]
benbrown has left #wayland [#wayland]
tyzef has quit [Quit: WeeChat 4.1.1]
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
mclasen_ has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Quit: Leaving]
fmuellner has quit []
mclasen has joined #wayland
fmuellner has joined #wayland
iomari892 has quit [Ping timeout: 480 seconds]
mclasen has quit []
mclasen has joined #wayland
Kerr has joined #wayland
leon-anavi has quit [Quit: Leaving]
narodnik has joined #wayland
mclasen has quit [Remote host closed the connection]