ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
feaneron has quit [Ping timeout: 480 seconds]
Consolatis_ has joined #wayland
Emantor_ has joined #wayland
aks has joined #wayland
vyivel_ has joined #wayland
pbsds4 has joined #wayland
bookworm_ has joined #wayland
any1_ has joined #wayland
andyrtr_ has joined #wayland
pbsds has quit [Read error: Connection reset by peer]
midgard has quit [Remote host closed the connection]
bookworm has quit [Remote host closed the connection]
Emantor has quit [Read error: No route to host]
vyivel has quit [Remote host closed the connection]
shoragan_ has joined #wayland
Consolatis is now known as Guest14348
Consolatis_ is now known as Consolatis
shoragan has quit [Ping timeout: 480 seconds]
midgard has joined #wayland
akselmo has quit [Ping timeout: 480 seconds]
Guest14348 has quit [Ping timeout: 480 seconds]
garnacho has quit [Ping timeout: 480 seconds]
andyrtr has quit [Ping timeout: 480 seconds]
andyrtr_ is now known as andyrtr
any1 has quit [Ping timeout: 480 seconds]
alarumbe has joined #wayland
bookworm_ is now known as bookworm
<orowith2os[m]>
mmmm, having troubles interpreting wl_keyboard regarding focus. What's the expected behavior from a compositor if I get a key pressed event, then lose focus entirely?
<orowith2os[m]>
should I get a key released event?
<orowith2os[m]>
oh, the leave event tells me. blech.
feaneron has joined #wayland
karenw_ has joined #wayland
Tom^ has quit [Quit: WeeChat 4.6.1]
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
karenw has quit [Ping timeout: 480 seconds]
dcz has joined #wayland
nerdopolis has quit [Ping timeout: 480 seconds]
dcz_ has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
kts has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
eluks has quit [Remote host closed the connection]
eluks has joined #wayland
danshick has joined #wayland
jkl has quit [Read error: Connection reset by peer]
<llyyr>
let me know if this right or not, I'm not 100% certain but it seems like chain_free is always called when switching surface configuration anyway
crazybyte4 has quit [Read error: Connection reset by peer]
kts has quit [Ping timeout: 480 seconds]
kts has joined #wayland
gusnan has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
karenw_ has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
<MrCooper>
orowith2os[m]: color-representation isn't really about colorimetry, it's about how to interpret the bits in pixel values
alarumbe has quit [Quit: ZNC 1.8.2+deb3.1+deb12u1 - https://znc.in]
glennk has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
___nick___ has joined #wayland
rasterman has joined #wayland
kts has joined #wayland
leon-anavi has joined #wayland
vyivel_ has quit [Remote host closed the connection]
vyivel has joined #wayland
JakeSays1 has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
___nick___ has quit [Remote host closed the connection]
<pq>
orowith2os[m], color-representation answers questions "Has alpha been already baked into RGB and how?" and "How to convert this YUV to RGB?". color-management answers the question "What does this RGB mean? How saturated? How luminous?".
<JEEB>
and for gamut/colorspace you can either have pre-defined "common" values for which you don't have to create a complex profile for yourself, or then the more historically common in image manipulation color profile which contains a more specific definition
<JEEB>
(although it seems like color profiles now contain the capability of definining those "common" values, which is how JPEG "got support" for those common values)
Calandracas_ has joined #wayland
Calandracas has quit [Ping timeout: 480 seconds]
naveenk2 has joined #wayland
JakeSays has joined #wayland
<naveenk2>
HI, do we need explictly enable color-management in weston? I dont see an easy way. So far, it is giving me 'color-manager: no-op' with upstream main
kestrel has joined #wayland
JakeSays1 has quit [Ping timeout: 480 seconds]
kts has quit [Ping timeout: 480 seconds]
JakeSays1 has joined #wayland
JakeSays has quit [Ping timeout: 480 seconds]
naveenk2 has quit [Ping timeout: 480 seconds]
kts has joined #wayland
kts has quit [Ping timeout: 480 seconds]
nerdopolis has joined #wayland
fatal has quit [Remote host closed the connection]
fatal has joined #wayland
<mvlad>
yes, needs to enabled explicitly in the core section.
riteo has quit [Remote host closed the connection]
tlwoerner has joined #wayland
kasper93 has quit [Read error: Connection reset by peer]
naveenk21 has joined #wayland
riteo has joined #wayland
<naveenk21>
Re-posting it: HI, do we need explictly enable color-management in weston? I dont see an easy way. So far, it is giving me 'color-manager: no-op' with upstream main