[02:24] <duflu> camako: Woo, 0.26.0 now contains 40 fixes. Big enough for you? :)
[12:12] <alan_g> dandrader: miral 1.0.2 has landed in archive
[12:12]  * dandrader checks
[12:15] <dandrader> alan_g, indeed, thanks
[12:25] <dandrader> alan_g, see this scenario. got top-level window A (focused and on top of the stack) followed by top-level window B and child window B1. B->activate() is called. miral raises only B1. Is that correct?
[12:26] <dandrader> (B1 was front of B, to be clear)
[12:46] <dandrader> alan_g, yes, reproduced it with miral-shell. indeed a bug
[13:07] <dandrader> alan_g, https://bugs.launchpad.net/miral/+bug/1658085
[13:20] <alan_g> dandrader: ack
[14:28] <dandrader> alan_g, is there a key to quit miral-shell?
[14:28] <alan_g> Ctrl-Alt-BkSp
[14:28] <dandrader> thanks
[14:44] <alan_g> bregma: miral-examples contains a useful scripts: miral-desktop (starts a "desktop") and miral-xrun (runs argument under Xmir)
[15:04] <alan_g> dandrader: https://code.launchpad.net/~alan-griffiths/miral/fix-1658085/+merge/315232
[15:04] <dandrader> alan_g, ack
[15:31] <alan_g> dandrader: am I right in assuming your child window stuff will sweep up bug 1656727?
[17:53] <dandrader> alan_g, yes. I get no crash here. just proper menus
[17:53] <dandrader> alan_g, will link the bug to the mp
[17:53] <alan_g> dandrader: great