=== no_mu is now known as Nothing_Much === greyback__ is now known as greyback === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun [11:33] anpok: your concerns are addressed now? https://code.launchpad.net/~mir-team/mir/introduce-pointer-event/+merge/245679 [11:46] yes === dandrader is now known as dandrader|afk === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === alan_g is now known as alan_g|lunch === dandrader|afk is now known as dandrader === chihchun is now known as chihchun_afk === alf is now known as alf_ === alan_g|lunch is now known as alan_g === chihchun_afk is now known as chihchun [13:34] alf_, would the asio->glib mainloop stuff affect this part of USC? [13:34] http://bazaar.launchpad.net/~mir-team/unity-system-compositor/devel-mir-next/view/head:/src/asio_dm_connection.cpp [13:36] kdub: no, that's an independent asio service instantiation [13:36] alf_, thanks [13:36] kdub: np === chihchun is now known as chihchun_afk [14:05] alf_: so should we also migrate usc onto glib mainloop ? curious the thot === seb128_ is now known as seb128 === alan_g is now known as alan_g|afk [14:19] kgunn: @USC glib, I would say no. The needs of the USC DM connection are very simple and a good match for what ASIO offers. The GLib event loop would be overkill for this. [14:20] ack === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === dandrader is now known as dandrader|lunch [16:39] There's no Mir connection mock, right? [16:39] I'm not going to write one, but I'd love to have one for my test :-) === dandrader|lunch is now known as dandrader === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === alan_g|afk is now known as alan_g === tedg` is now known as tedg === irsol_ is now known as irsol === DalekSec_ is now known as DalekSec