Robert Andrew Ditthardt
Robert Andrew Ditthardt
lgi is creating a separate event loop for each async call context? I've been extending my config with more and more async contexts as I go. I have seen 0...
I see what you're saying. Yeah, the biggest problem with async code is the lack of a straightforward call stack...things get lost in the event loop. That said, I think...
Just for fun I tested your patch and unfortunately I'm still seeing the exact same log messages. Is it possible that glib is treating the second loop as just more...
There seems to be less of the messages but I'm still getting them. My hunch is that it's from creating nested loops. My config is more complex then the case...
What about only processing x events in the main loop started by awesome and ignoring the rest? Based on testing I've done, events in the first loop are still processed...
not a bad idea! how about just "file" though?
Feel free to make a PR and reference this issue