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]
guru__ has joined #wayland
fmuellner has quit [Ping timeout: 480 seconds]
guru_ has quit [Ping timeout: 480 seconds]
columbarius has joined #wayland
co1umbarius has quit [Ping timeout: 480 seconds]
aknot has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
<Tim-Rex>
Wasn't quite sure where to go to ask this, but I have a question about implementing a wayland client application.. Is there a provided Wayland mechanism to generate and receive user-defined message types?
<Tim-Rex>
Specifically, I'm wanting to signal my wayland client application from another thread, and unsure what the recommended approach is for a well behaved Wayland application.
<Tim-Rex>
I could certainly use non-wayland facilities to do that (shared memory, some other signalling) but something using the wayland event loop seems perhaps a better way to go (if that's a facility that is offered)
<orowith2os[m]>
Tim-Rex: if it doesn't involve other Wayland clients, or the compositor, you can use your own mechanism
<orowith2os[m]>
Wayland doesn't really get a say in what the client does for thread communication in the client
<Tim-Rex>
Okay, that works. Thanks for confirming @orowith2os
mxz has quit [Ping timeout: 480 seconds]
Tim-Rex has quit [Remote host closed the connection]
riteo_ has joined #wayland
riteo has quit [Ping timeout: 480 seconds]
glennk has joined #wayland
mxz has joined #wayland
tzimmermann has joined #wayland
garnacho has joined #wayland
mvlad has joined #wayland
ofourdan has joined #wayland
sima has joined #wayland
mripard has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
karolherbst_ has joined #wayland
karolherbst has quit [Read error: Connection reset by peer]
Leopold___ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
Dami_Lu has joined #wayland
Dami_Lu has quit [Remote host closed the connection]
kts has joined #wayland
Dami_Lu has joined #wayland
kts has quit [Ping timeout: 480 seconds]
Leopold_ has quit [Read error: Connection reset by peer]
Leopold has quit [Remote host closed the connection]
Leopold has joined #wayland
Leopold has quit [Remote host closed the connection]
Leopold_ has joined #wayland
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
<any1>
Is di_info_get_edid supposed to return a decent error message? It looks like most failure messages just get discarded because NULL is returned, so you can't get get the failure message from the info object.
<emersion>
hm, i don't think we set an error message when we return NULL?
<emersion>
do you have an example in mind?
<emersion>
but yeah, that's a known defect of the API
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #wayland
kts has quit [Ping timeout: 480 seconds]
navi has quit [Ping timeout: 480 seconds]
fmuellner has joined #wayland
<Vaughn>
While I acknowledge I should presumably be trying to debug it instead... is it possible to disable high-resolution wheel scrolling in Wayland?