=== chihchun_afk is now known as chihchun [01:18] So, *of course* I'm unable to reproduce the failures on https://code.launchpad.net/~mir-team/mir/surface-output-events/+merge/272698 locally. [01:18] That would be too easy. [04:02] RAOF: -"just landed" +"about to land" [04:02] I guess technically top-approved ≠ landed, but it's pretty close :) [04:03] What could possibly go wrong? :) [04:11] Oh, hah. [04:12] Android tests fail because Android is hilariously unprepared for being sent disconnected displays. [04:12] Fixes are pending [04:12] Also, Marshmallow images now exist. If you're into such things. [05:06] Huh. [05:06] Have we managed to make Mir fail to build without precompiled headers? [05:09] it happens now and then that headers are missing from tests [05:09] Yeah. [05:09] i believe we dont have a slow build ci job.. [05:11] One of our amd64 builds would be a good idea. [05:11] Jenkaas. [05:11] hm which drm headers should we use? [05:12] only one got updated with the new cursor cap enums.. but I believe that one is inherently c++ unfriendly [05:12] xf86drm.h is the right one, no? [05:12] (And friends) [05:13] it pulls in .. [05:14] hm which with our config then pulls in libdrm/drm.h I believe [05:17] Hm. [05:17] I think it's going to be a multi-hundred-line diff to make Mir build without precompiled headers :) [08:43] alf: what's the ETA for branching 0.17? (I'd like to sneak an API tweak through beforehand to avoid breaking in 0.18) [08:45] alan_g: A couple of days. I am still waiting for a few required fixes/improvements to land. [08:45] alf: perfect. :) [08:48] * guest42315 waiting for xmir :( [08:50] * anpok just thinks about the 32k lines change he wants to sneak in [08:51] anpok: I want that one too. Just need a bit of time to check it [08:52] hm the krillins we have in ci seem to behaving different.. [08:52] or is that caused by my mps.. [10:11] hi all, apologies if this is the wrong forum or if it's an FAQ already, but is Xmir supposed to work in Wily desktop for either Unity7 or Unity8 sessions? [10:15] shiznix: there are a lot of problems with Xmir. They're across a range of dependencies and I doubt they'll all land in Wily now it has hit feature freeze. duflu is probably best informed. [10:15] shiznix: No, the new incarnation of Xmir is not ready for general consumption [10:19] why does clang prefer initializing members over just using the default copy constructor in template contexts when it parsers something{something_of_the_same_type} [10:20] ok thanks, i'll hold off on bug reports re. Black Screen of Death then ;) [10:20] -r === chihchun is now known as chihchun_afk [10:32] alf: the MP I want to sneak into 0.17: https://code.launchpad.net/~alan-griffiths/mir/tweak-cursor-configuration/+merge/273512 [10:35] alan_g: ack === alan_g is now known as alan_g|lunch === alan_g|lunch is now known as alan_g [14:31] alan_g, should I be able to see the mir cursor on a nexus 7? [14:31] alan_g, I'm trying to debug something and being able to see what the mir cursor is up to would help a lot [14:31] dandrader: I thought you had code to hide it? [14:32] alan_g, that's with a nexus 7 I just flashed. my code to hide mir cursor hasn't landed yet [14:32] alan_g, I can see mir cursor on my laptop just fine [14:32] alan_g, and that's what I've been using for development [14:33] alan_g, but now I started testing things on the nexus 7 [14:33] alan_g, and there's a problem where, unity8 stops receiving mouse events from usc [14:33] alan_g, likely because the mir mouse pointer is not over any of unity8' [14:33] s surfaces [14:33] dandrader: I don't know of any special case code. But whether it works on N7 I don't know [14:36] Something, somewhere hides the cursor on phablet (or maybe it is not detecting the mouse?) [14:39] alan_g, unity8 is getting mouse events and its ui is responding to them. I just don't see the mir mouse pointer on the screen. not a big deal. just wanted a visual clue of mir cursor whereabouts to help with my debugging. can achieve the same result but with some more work. [14:40] hmmm..... thinking better about it. I think I know what's the problem with mouse events when I connect an external monitor [14:41] I have unity8 drawing its shell on the external monitor and I draw a full screen notice on the built-in display [14:41] the qml mouse in the shell moves fine [14:41] up to a point [14:42] dandrader: alan_g: I don't know if it's related to your setup, but USC explicitly disables the cursor [14:42] if I go anywhere near the left edge (I mean x less than 1/4 of the screen width) [14:42] the mouse stops moving [14:43] I guess it's because the mir mouse moved away from the external monitor area onto the built-in display [14:43] since the mir cursor has acceleration it moves faster the qml one (relative movement that the qml cursor consumes is not accelerated atm) [14:43] alf, only on android, right? [14:46] dandrader: yes (AFAIK) === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === alan_g is now known as alan_g|EOD === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader