=== chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === hikiko is now known as hikiko|bbl === chihchun_afk is now known as chihchun [09:26] greyback: can I draw your attention to the changes in miral-qt/src/platforms/mirserver/windowmanagementpolicy.cpp here: https://code.launchpad.net/~alan-griffiths/miral/reduce-WindowManagerTools/+merge/301885 - possibly something you're aware of already? [09:27] alan_g: the fact there was overlap did occur to me, I just considered it a convenience thing. I've no problem removing it === JanC is now known as Guest88920 === JanC_ is now known as JanC [09:29] "removing" == deleting these functions? [09:45] greyback: is ltinkl away for longer? [09:51] alan_g: yep [09:52] anpok: longer than a piece of string? :) [09:52] anpok: he was online yesterday, i don't think he's on holidays [09:52] greyback: Ok, I'll do that instead. ;) [10:08] greyback: I am looking at qtubuntu and an input filter plugin called qcomposeplatforminputcontextplugin [10:08] can you shed some light on what part decides whether a plugin like that would be loaed [10:09] .. it currently is not.. so thats why ubuntu touch is not handling compose sequences.. [10:13] anpok: could you try testing with this env var set: QT_IM_MODULE="compose" === hikiko|bbl is now known as hikiko [10:14] I see the XCB qpa plugin has a cheeky qputenv("QT_IM_MODULE", QByteArray("compose")); [10:14] we might need to duplicate that === chihchun is now known as chihchun_afk [10:18] ok [10:18] it works on desktop qt [10:18] with unity8 [10:19] so .. I was wondering if that env var could be a list? because we stil need malitt too [10:19] or maybe because we dont have maliit loaded on desktop it falls back and loads the compose plugin.. === chihchun_afk is now known as chihchun [10:23] anpok: I'm not sure, need to read more [10:24] QPlatformInputContextFactory obviously only creates one instance [10:26] greyback: hm we could implement compose sequences in mir.. i had hopped it would not be necessary [10:27] greyback: QT_IM_MODUE=compose does the trick.. [10:27] and breaks maliit [10:28] I don't see an obvious way they can co-exist in Qt [10:29] only idea is to create a QCombinationInputContext class, which imports both maliit & compose plugins underneath [10:29] hm we could extend maliitphablet to handle keys and include the compose key handlng there.. [10:32] do we really need support for OSK and physical keyboard at the same time? [10:33] hm probably not === chihchun is now known as chihchun_afk [12:10] alan_g: small api comment with miral::WindowInfo - any reason you don't use mir::geometry::Size for min/max sizes? [12:11] and for the increment, would not an increment of 1 be the same as having no increment set? [12:58] greyback: I guess. IIRC it was all optional (so width could be set without height) and I simplified by always having min/max with 0/numeric_limits<>::max. You're right the same could be done with increments. [12:59] But... I think there's some independence between min_width and min_height and they shouldn't be combined in one value. [13:02] alan_g: sure, they're independent values. I just thought the Size type was a natural container for the pair of vals [13:02] no biggie anyway [13:16] greyback: I'll pick up the change to increments though [13:16] ok === chihchun_afk is now known as chihchun [14:29] alf_: you've approved two miral MPs (thanks!) but not looked at the prerequisite? === chihchun is now known as chihchun_afk [14:33] alan_g: looking [14:34] thanks === Celtor is now known as vitimiti [14:45] greyback: https://code.launchpad.net/~alan-griffiths/miral/simplify-size-increments/+merge/301909 === dandrader is now known as dandrader|afk [14:47] alan_g: approved! [14:53] alf_: reworded https://code.launchpad.net/~alan-griffiths/miral/add-introducing_the_miral_api/+merge/301779 - better? [14:55] alan_g: a question: have you a plan on how SurfaceObserver fits in with miral's api? [14:56] say if a window is repositioned, both SurfaceObserver::moved_to and WMPolicy::advise_move_to will fire [14:57] yes. (But SurfaceObserver isn't in the MirAL API) [15:00] ok, I'll try to avoid relying on SurfaceObserver === dandrader|afk is now known as dandrader === JanC is now known as Guest94529 === JanC_ is now known as JanC [17:52] Hello. [17:53] http://bazaar.launchpad.net/~mir-team/mir/development-branch/view/head:/src/platforms/android/server/device_quirks.cpp#L176 [17:53] Why the pixel format is hard-coded to mir_pixel_format_abgr_8888? [18:30] that is only used to query information about the gpu.. [18:30] do you ran into problems with that? [18:37] anpok: Well, the problem is my device don't support that format. [18:38] As the context is created, an exception gets thrown. [18:39] "std::exception::what: could not select EGL config for use with framebuffer" [18:39] peat-psuwit: hm then you could write a function that tests the device name and in your case returns a differen pixel format .. [18:39] make an MP for that.. [18:42] anpok: Actually, I have another idea. I'll put that in try-catch block. If that failed, then try another format. [18:42] Thanks for your idea anyway. === dandrader is now known as dandrader|afk === dandrader|afk is now known as dandrader