ChanServ changed the topic of #wayland to: https://wayland.freedesktop.org | Discussion about the Wayland protocol and its implementations, plus libinput
<jumpingAI>
we saw lot's of birtish trash scout boys who demonstrated their non-existent amoeba one brain cell skills to their ladies like The crook Dave Airlie , we deliver them in coffin to the last road soon, planted another biochip to harvest testosterone, i am aware of this again, they get opted for removal before i join billionaire club, The British human garbage
<ammen99>
Hello, I am debugging a weird crash in my compositor and I am wondering, is it possible to get any more events on an event source created with wl_event_loop_add_fd, after wl_event_source_remove is called (note that _remove() is called from inside the handler for the fd events)?
rasterman has quit [Quit: Gettin' stinky!]
Brainium has joined #wayland
<emersion>
shouldn't be possible since remove() destroys the event source
<ammen99>
ok I wasn't sure what it does exactly (from the implementation) I thought maybe it could become inert and still some random poll could return that it is still active
<ammen99>
thanks
<emersion>
hm, right, it's not straightforward indeed, but reading in more detail i don't think this can happenb
<emersion>
it removes from the list and sets fd=-1
iomari892 has joined #wayland
<ammen99>
oh yeah and then the _dispatch() checks it I see it now
iomari891 has quit [Ping timeout: 480 seconds]
tzimmermann has quit [Quit: Leaving]
iomari892 has quit [Remote host closed the connection]
Brainium has quit [Quit: Konversation terminated!]
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #wayland
iomari891 has joined #wayland
DodoGTA has quit [Quit: DodoGTA]
DodoGTA has joined #wayland
DodoGTA has quit []
DodoGTA has joined #wayland
DodoGTA has quit []
DodoGTA has joined #wayland
kts has joined #wayland
kts has quit []
kts has joined #wayland
nahtaiv3l has joined #wayland
nahtaiv3l has quit [Quit: ERC 5.5.0.29.1 (IRC client for GNU Emacs 29.3)]
ahartmetz has quit [Quit: Konversation terminated!]
ahartmetz has joined #wayland
neniagh has quit [Read error: No route to host]
caveman has joined #wayland
Brainium has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
Brainium has joined #wayland
lsd|2 has joined #wayland
Brainium has quit [Ping timeout: 480 seconds]
DodoGTA has quit [Quit: DodoGTA]
Brainium has joined #wayland
ity has quit [Remote host closed the connection]
iomari892 has joined #wayland
iomari891 has quit [Ping timeout: 480 seconds]
rasterman has joined #wayland
cyrinux3 has quit []
cyrinux3 has joined #wayland
iomari891 has joined #wayland
iomari892 has quit [Ping timeout: 480 seconds]
DodoGTA has joined #wayland
alice has quit [Remote host closed the connection]
alice has joined #wayland
Brainium has quit [Quit: Konversation terminated!]
alice has quit [Remote host closed the connection]
alice has joined #wayland
alice has quit [Remote host closed the connection]
<xjuan>
same as me but its not calling wl_event_loop_dispatch_idle()
<xjuan>
wl_event_loop_dispatch() does not dispatch idle sources
<feaneron>
if you're mixing wl_event_loop and GSource, is there anything in particular that prevents you from using GLib idle sources instead of Wayland idle sources?
<xjuan>
not really
<xjuan>
but I am using wlroots
<xjuan>
and they are using wayland idle sources
<xjuan>
I can workaround by setting a check flag in the source after I make the call to the function that queue the idle
<xjuan>
but that is kind of a hack
<xjuan>
I rather have a proper way to handle all the idles
leon-anavi has quit [Remote host closed the connection]
Guest1256 has quit [Remote host closed the connection]
cool110 has joined #wayland
cool110 is now known as Guest1317
privacy has quit [Quit: Leaving]
sergio_ has joined #wayland
sergio_ has quit []
Brainium has quit [Quit: Konversation terminated!]