ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
glennk has quit [Ping timeout: 480 seconds]
rgallaispou has quit [Ping timeout: 480 seconds]
lsd|2 has joined #wayland
lsd|2 has quit []
fmuellner has quit [Ping timeout: 480 seconds]
Brainium has quit [Quit: Konversation terminated!]
Moprius has quit [Remote host closed the connection]
phryk_ has joined #wayland
phryk has quit [Read error: Connection reset by peer]
garnacho has quit [Ping timeout: 480 seconds]
kts has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
user21 has quit [Ping timeout: 480 seconds]
midgard has quit [Quit: Bye]
eluks has quit [Remote host closed the connection]
eluks has joined #wayland
midgard has joined #wayland
user21 has joined #wayland
user21 has quit [Quit: Leaving]
user21 has joined #wayland
juwain has joined #wayland
glennk has joined #wayland
pavlushka has joined #wayland
kts has quit [Ping timeout: 480 seconds]
zvarde1988303206779191685873 has joined #wayland
zvarde198830320677919168587 has quit [Ping timeout: 480 seconds]
zvarde1988303206779191685873 is now known as zvarde198830320677919168587
sima has joined #wayland
tzimmermann has joined #wayland
garnacho has joined #wayland
leon-anavi has joined #wayland
mvlad has joined #wayland
rgallaispou has joined #wayland
MrCooper_ is now known as MrCooper
rasterman has joined #wayland
rasterman has quit []
rgallaispou has quit [Read error: Connection reset by peer]
ofourdan has joined #wayland
juwain has quit []
Moprius has joined #wayland
fmuellner has joined #wayland
fmuellner has quit [Remote host closed the connection]
fmuellner has joined #wayland
p7cq4 has joined #wayland
p7cq has quit [Read error: Connection reset by peer]
p7cq4 is now known as p7cq
kts has joined #wayland
vincejv has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
Brainium has joined #wayland
lockywolf has quit [Read error: Connection reset by peer]
pavlushka has quit [Ping timeout: 480 seconds]
vincejv has joined #wayland
iomari891 has joined #wayland
lockywolf has joined #wayland
lsd|2 has joined #wayland
m5zs7k has quit [Ping timeout: 480 seconds]
m5zs7k has joined #wayland
tlwoerner_ has joined #wayland
tlwoerner has quit [Ping timeout: 480 seconds]
pavlushka has joined #wayland
<zamundaaa[m]>
pq: the color MR turns 5 years old tomorrow
<zamundaaa[m]>
A good day to merge it?
leonanavi has joined #wayland
leon-anavi has quit [Ping timeout: 480 seconds]
tlwoerner has joined #wayland
MrCooper has quit [Read error: Connection reset by peer]
MrCooper has joined #wayland
tlwoerner_ has quit [Ping timeout: 480 seconds]
<MrCooper>
would be a neat coincidence, shouldn't rush anything for that though
pavlushka has quit [Remote host closed the connection]
pavlushka has joined #wayland
karenw has joined #wayland
<karenw>
Hi. So trying to implement touch support in my example client. Am I right in thinking there is not a single 'focus' for the whole seat like wl_pointer and wl_keyboard, but each touchpoint has it's own wl_surface?
<vyivel>
karenw: yes
<karenw>
Excellent. Glad I understand ;)
<karenw>
This makes me think my pointer tracking of focus is a bit nobbled. Since there can be a frame() event after leave(). I guess I should only forget or change the focus in frame(). Urgh.
<swick[m]>
zamundaaa: given that we still have API breaking MRs open that feels a bit rushed
coldfeet has joined #wayland
<zamundaaa[m]>
It's hard to call anything "rushed" when talking about a protocol that's been in development for over a decide, a MR that's 5 years old and has many implementations in compositors and clients
<zamundaaa[m]>
That one MR should be decided on before merging the protocol of course, but that should be done in a reasonable time frame
<orowith2os[m]>
I noticed that https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/294 hasn't had too much activity, and there's not really much pushback against it. It looks like there's desire from GNOME for it to land (then they'll add cursor-shape-v2 to mutter and gtk), Jay has a MR for it, wlroots has a MR for it, and zzag is fine with it. Is there anything that needs to be done there?
<karenw>
What should happen if I get the following touch events? Down Frame Up Cancel. Is the touchpoint still valid?
<karenw>
I assume not, because of the 'up'. But then what happens if I get "Up Down Frame" with the same id? That's a new touchpoint inside the same frame?
coldfeet has quit [Quit: Lost terminal]
mclasen has quit [Remote host closed the connection]
nerdopolis has joined #wayland
fangzhoug has joined #wayland
<karenw>
Interesting, mutter increments the touchpoint id every touch, but kwin/weston/sway all reuse low numbers.
<karenw>
Both are within spec though, right?
<vyivel>
yes
mohit815822635306 has quit [Quit: mohit815822635306]
mohit815822635306 has joined #wayland
karenw has quit [Quit: Deep into that darkness peering...]
pavlushka has quit [Ping timeout: 480 seconds]
karenw has joined #wayland
karenw has quit []
rasterman has quit [Quit: Gettin' stinky!]
karenw has joined #wayland
<orowith2os[m]>
swick: random question, how does color-management-v1 deal with black-and-white displays?
<orowith2os[m]>
granted I'm not sure if it's dealt with literally anywhere else within Linux
<orowith2os[m]>
I know you mentioned communicating color deficiencies to applications on xdp, maybe this would help?
<orowith2os[m]>
or do you want something else for that?
karenw has quit [Quit: Deep into that darkness peering...]
<swick[m]>
If you don't have colors, you wouldn't implement it
<swick[m]>
technically you still could but it would be almost pointless
<swick[m]>
s/implement/expose
<orowith2os[m]>
gotcha
<orowith2os[m]>
so it would need to be exposed some other way
<swick[m]>
the protocol is about content and displays, not about the observer, so color deficiencies are not well suited there
<orowith2os[m]>
I guess so. I'll have to take a closer look at the protocol to see if it can't be reasonably added to that
<orowith2os[m]>
primaries wouldn't work?
<swick[m]>
CVD don't just change some "primaries"
<orowith2os[m]>
hmm
<swick[m]>
CVDs are often the result of changes in the responsiveness of the photo cells
<orowith2os[m]>
what would communicating the fact that the display is grayscale look like, in your ideal world?
karenw has joined #wayland
<swick[m]>
not sure
<swick[m]>
the only grayscale displays that I'd think would be reasonable to run a full wayland compositor on are probably eink displays, and they come with a whole bunch of unsolved issues
<emersion>
yeah, need a whole lot more than just "the display is black-and-white/grayscale"
karenw has quit []
karenw has joined #wayland
<orowith2os[m]>
I guess if a hardware platform is using eink in general, wayland just wouldn't be useful, considering part of their use cases is low power draw (and using normal desktop software might not get that)
<orowith2os[m]>
but this issue is still kind of there with desktop-oriented eink displays
<karenw>
Isn't it currently baked into the wl_compositor protocol that argb8888 and xrgb8888 are ubuquitous?
<orowith2os[m]>
and maybe statistics on embedded systems, like an rpi....
<orowith2os[m]>
whew, $700 for an eink display to use with a normal desktop..... glad we don't have to deal with that just yet.
<Arnavion>
<orowith2os[m]> I guess if a hardware platform is using eink in general, wayland just wouldn't be useful < Users of the PineNote (e-ink tablet) were running Sway and GNOME Wayland on it I believe. There might've been some patches or custom themes involved
<emersion>
karenw: the compositor can convert to grayscale as a fallback. that's what some KMS drivers do for instance
feaneron has joined #wayland
user21 has quit [Ping timeout: 480 seconds]
grinja1 has quit [Remote host closed the connection]
grinja1 has joined #wayland
mvlad has quit [Remote host closed the connection]
user21 has joined #wayland
pounce has quit [Remote host closed the connection]
pounce has joined #wayland
karenw_ has joined #wayland
karenw is now known as Guest6704
karenw_ is now known as karenw
Guest6704 has quit [Ping timeout: 480 seconds]
user21 has quit [Ping timeout: 480 seconds]
AJ_Z0 has quit [Quit: I have to return some videotapes]
AJ_Z0 has joined #wayland
glennk has quit [Read error: Connection reset by peer]