=== JanC is now known as Guest74845 === JanC_ is now known as JanC === lpotter_ is now known as lpotter [14:15] greyback, a simple one: https://code.launchpad.net/~dandrader/qtubuntu/winIdIsMirSurface/+merge/296794 [14:16] dandrader: I think mir has api for surfaces to get a persistent ID. That would be more suitable than a pointer [14:16] greyback, oh, it's missing the prereq. just a sec [14:17] greyback, there https://code.launchpad.net/~dandrader/qtubuntu/winIdIsMirSurface/+merge/296795 [14:18] greyback, you need a pointer to refer to the surface in mir's client API [14:18] greyback, and that's unique from the applications point of view [14:19] greyback, it's used here: http://bazaar.launchpad.net/~dandrader/ubuntu-keyboard/mirSurfaceInputBounds/revision/473 [14:20] greyback, in src/plugin/mirinputregionupdater.cpp [14:20] greyback, will propose those other branches once I'm finished with testing. but got diverted by https://bugs.launchpad.net/qtmir/+bug/1588929 [14:20] Launchpad bug 1588929 in QtMir "cursor interactions cause lockup with pocket desktop" [Undecided,In progress] [14:21] dandrader: sure, but winId() is more suited to the persistent ID that works across processes. Say process A wants to child its window to process B, IMO winId is way to communicate that [14:25] I think the native window interface thingy would be good enough to return the raw mir pointer to a qwindow [14:25] greyback, so you want it to return MirPersistentId then. Then how do you suggest an app to get the MirSurface* of its QWindow? [14:27] dandrader: I think we already do in QPlatformNativeInterface::windowProperty [14:28] well our subclass of it [14:42] Saviq, tsdgeos: hey! Could you guys help me out and give https://requests.ci-train.ubuntu.com/#/ticket/1498 a spin once you have a minute? [14:43] sil2100: yes [14:43] Thanks :) [15:08] sil2100: works fine here \o/ [15:09] Wooo \o/ [15:09] tsdgeos: thanks! [15:29] hi alicia === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader [20:38] cimi: https://code.launchpad.net/~3v1n0/ubuntu-settings-components/cmake-staging-install-fix [23:25] I'm not seeing updates to Unity 8 desktop on 16.04, yet 16.10 seems to be ahead in develpment. Is 16.04 Unity 8 'parked'? [23:42] jarlath, you have stable phone overlay PPA? [23:44] cimi : No, the standard unity8-desktop in the 16.04 archive. I'm told phone overlay hasn't got the desktop components [23:46] jarlath, we still use that PPA as base, the stack is the same, if you can upgrade 16.10 will have what's most recent [23:47] Thanks cimi. Might do that. Is the plan going forward to move with the releases? [23:48] jarlath, I am going to upgrade soon over the next weeks, but so far I develop in xenial + phone overlay PPA [23:48] jarlath, then every once a while we do landings and we create PPA for testing new features [23:49] but you shouldn't worry about those, they might break things :) [23:49] cimi, thats good enough for me. Ill go with phone overlay :) Thanks again. [23:51] jarlath, you're welcome :)