| === JanC is now known as Guest74845 | ||
| === JanC_ is now known as JanC | ||
| === lpotter_ is now known as lpotter | ||
| dandrader | greyback, a simple one: https://code.launchpad.net/~dandrader/qtubuntu/winIdIsMirSurface/+merge/296794 | 14:15 |
|---|---|---|
| greyback | dandrader: I think mir has api for surfaces to get a persistent ID. That would be more suitable than a pointer | 14:16 |
| dandrader | greyback, oh, it's missing the prereq. just a sec | 14:16 |
| dandrader | greyback, there https://code.launchpad.net/~dandrader/qtubuntu/winIdIsMirSurface/+merge/296795 | 14:17 |
| dandrader | greyback, you need a pointer to refer to the surface in mir's client API | 14:18 |
| dandrader | greyback, and that's unique from the applications point of view | 14:18 |
| dandrader | greyback, it's used here: http://bazaar.launchpad.net/~dandrader/ubuntu-keyboard/mirSurfaceInputBounds/revision/473 | 14:19 |
| dandrader | greyback, in src/plugin/mirinputregionupdater.cpp | 14:20 |
| dandrader | 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 |
| ubot5 | Launchpad bug 1588929 in QtMir "cursor interactions cause lockup with pocket desktop" [Undecided,In progress] | 14:20 |
| greyback | 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:21 |
| greyback | I think the native window interface thingy would be good enough to return the raw mir pointer to a qwindow | 14:25 |
| dandrader | greyback, so you want it to return MirPersistentId then. Then how do you suggest an app to get the MirSurface* of its QWindow? | 14:25 |
| greyback | dandrader: I think we already do in QPlatformNativeInterface::windowProperty | 14:27 |
| greyback | well our subclass of it | 14:28 |
| sil2100 | 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:42 |
| tsdgeos | sil2100: yes | 14:43 |
| sil2100 | Thanks :) | 14:43 |
| tsdgeos | sil2100: works fine here \o/ | 15:08 |
| sil2100 | Wooo \o/ | 15:09 |
| sil2100 | tsdgeos: thanks! | 15:09 |
| lborda | hi alicia | 15:29 |
| === dandrader is now known as dandrader|afk | ||
| === dandrader|afk is now known as dandrader | ||
| Trevinho | cimi: https://code.launchpad.net/~3v1n0/ubuntu-settings-components/cmake-staging-install-fix | 20:38 |
| jarlath | 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:25 |
| cimi | jarlath, you have stable phone overlay PPA? | 23:42 |
| jarlath | cimi : No, the standard unity8-desktop in the 16.04 archive. I'm told phone overlay hasn't got the desktop components | 23:44 |
| cimi | 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:46 |
| jarlath | Thanks cimi. Might do that. Is the plan going forward to move with the releases? | 23:47 |
| cimi | jarlath, I am going to upgrade soon over the next weeks, but so far I develop in xenial + phone overlay PPA | 23:48 |
| cimi | jarlath, then every once a while we do landings and we create PPA for testing new features | 23:48 |
| cimi | but you shouldn't worry about those, they might break things :) | 23:49 |
| jarlath | cimi, thats good enough for me. Ill go with phone overlay :) Thanks again. | 23:49 |
| cimi | jarlath, you're welcome :) | 23:51 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!