[06:57] <RAOF> GAH! CachedPtr strikes again!
[07:02] <RAOF> ...and EOD>
[11:08] <alan_g> greyback: I've been poking around miral-qt again. Fixed (subject to review) some stuff that needed fixing.
[11:08] <greyback> alan_g: ack. I've just opened the queue
[11:12] <greyback> alan_g: looking at https://code.launchpad.net/~alan-griffiths/miral/remove-some-modules-Unity-Application-dependence-on-libmirserver-dev/+merge/309593 - you move the mirserver dependency into a small helper utility - is that all you will do with that, or have you further plans?
[11:16] <alan_g> greyback: it's a process, I first want to isolate the precise features that are being used, and then review how (or if) they should look in libmiral. I suspect some are not yet stable enough and am wondering about an "experimental" library to move them to for now.
[11:22] <greyback> alan_g: ok. Wanted to be clear on the direction
[11:27] <alan_g> Sure. In this case it makes it clear how little of the mir/scene/session.h interface is used.
[16:12] <alan_g> greyback_: just wondering... why does Mir "Need api for client to inhibit screen dim/off" when AFAICS it is no more involved than in "cut&paste" or "drag&drop"?
[16:14] <greyback_> alan_g: you could look at it that way, yes. But I believe copy&paste/dnd were designed with as little mir involvement due to the content-exchange aspect.
[16:15] <greyback_> whereas this strikes me as very close to mir's existing functionality - display configuration
[16:17] <alan_g> But repowerd manages screen dim/off. The only thing needed is "what's the current app?"
[16:17] <alan_g> Which is almost the same as C&P
[16:18] <greyback_> I'd say current focusedwindow more than current app, but you point remains
[16:23] <alan_g> thanks