[08:04] <duflu> robert_ancell: Could just about do another Xmir release now. The most important bugs of the moment are fixed. I'm just trying to figure out how to fix up launchpad git so that 1.18 is the default branch...?
[08:05] <robert_ancell> duflu, I've changed the default
[08:05] <duflu> robert_ancell: Thanks. I assume I couldn't see it without admin
[08:06] <robert_ancell> It was https://code.launchpad.net/~xmir-team/xorg-server/+git/xmir/+edit
[08:06] <robert_ancell> probably admin required
[08:06] <duflu> Nope, I just lacked the URL
[08:07] <duflu> robert_ancell: I do want to try for more Xmir fixes but no need to wait... I might achieve zero more in the short term
[08:07] <robert_ancell> ok, I'll upload to Yakkety
[08:08] <duflu> Ta
[08:21] <duflu> robert_ancell: Ha. I just landed another one, but not important
[08:21] <robert_ancell> duflu, I just noticed... :P
[08:23] <duflu> Well nobody else ever noticed that one but me. So you don't need to include it this time
[08:31] <alan_g> greyback: https://code.launchpad.net/~alan-griffiths/mir/add-mir_surface_spec_attach/+merge/300202/comments/774172
[08:45] <greyback> alan_g: replied. MirPlacement wfm
[08:46] <alan_g> greyback: ta
[09:14] <alan_g> greyback: I'm looking into exposing output changes in miral and was wondering about miral-qt/src/platforms/mirserver/screen.h - are any of the second block of methods actually used anywhere? Or are they just there because its easy?
[09:15] <greyback> alan_g: scale, formfactor, etc?
[09:17] <alan_g> I'm mostly thinking of pixelFormats(), modes() which I don't see used in the project and are not overrides
[09:18] <greyback> alan_g: mostly because they were easy
[09:19] <greyback> possibly cruft left over
[09:19] <greyback> I don't see any reason to keep them
[09:19] <alan_g> There's no "magic" access to them then from downstream?
[09:21] <alan_g> greyback: thanks, if I don't need to support them (yet) I won't.
[09:22] <greyback> alan_g: not that I'm aware of
[10:54] <greyback> alan_g: hey, from miral::WindowInfo, how can I distinguish a window having a parent or not? WindowInfo::parent() returns a Window, but it could be null
[10:55] <greyback> i.e. default instantialized
[10:55] <alan_g> I use "if (auto parent = info.parent())" a lot
[10:56]  * greyback never likes that syntax. I read the operation as assignment, which I never think of as being able to fail
[10:57] <greyback> alan_g: ok, that'll work
[10:57] <greyback> ta
[10:58] <alan_g> 1. it isn't assignment, 2. the result of assignment isn't success/fail
[10:59] <alan_g> greyback: how close are we to having something we can demo rendering using Qt?
[11:01] <greyback> alan_g: I have rendering, I'm working on the surface positioning now
[11:03] <alan_g> Isn't that just implementing the "advise_xxx" hooks?
[11:05] <greyback> alan_g: yep, but child window positions not correct, digging into why
[11:06] <alan_g> if you need help I'm interested
[11:06] <greyback> alan_g: ack
[11:07]  * alan_g has been fixing "window positions not correct" reported from toolkits for a couple of weeks
[11:10] <greyback> I think it's my issue, as miral-shell is working correctly
[11:10] <alan_g> It *could* be missing "advise" calls - I found a few
[11:17]  * alan_g remembers he wanted to provide an optional logging wrapper around the WMP
[13:00]  * camako sees that 0.23.4 has landed