[09:31] <mzanetti> vesar__, meeting time
[10:06] <dandrader> greyback, hey
[10:08] <greyback> dandrader: hi
[10:12] <dandrader> greyback, so, moving the Cursor to unity8 will be trickier than expected. I gonna have to move all parts involved to this new unity8 component
[10:13] <dandrader> greyback, and then add some sort of API between qtmir and this component, like a new QQuickWindow event type.
[10:22] <greyback> dandrader: cursor loader moves to u8, that's ok. But can not a component live in qtmir which does (1) signals when cursor moves, in relative coords and (2) indicates what cursor name should be used
[10:22] <greyback> is the later the API you're referring to?
[10:27] <dandrader> greyback, all parts are tightly coupled in the current design. Main issue being that MousePointer needs CursorImageProvider to get the current hotspot info
[10:27] <dandrader> greyback, so not obvious how to break them apart
[10:28] <greyback> hmm
[10:28] <dandrader> greyback, so I have to move MousePointer also to unity8
[10:29] <dandrader> greyback, so all that is left in qtmir is the PlatformCursor and and QtEventFeeder
[10:29] <dandrader> greyback, then have to figure out a nice way to make the qtmir part talk to the unity8 component
[10:30] <dandrader> greyback, but not sure it's really worth the effort... you sure we have to do this split? :)
[10:33] <greyback> dandrader: I'm trying to think of alternatives
[10:35] <dandrader> greyback, it's actually not bad to move it all into a component. but thing is, this split seems to require some substantial refactoring/redesign effort
[10:36] <greyback> dandrader: I know. But I think it's worth it.
[10:38] <greyback> I think MousePointer & CursorImageProvider should live in unity8.
[10:39] <dandrader> greyback, ok, will continue the work then
[10:39] <greyback> thanks
[11:12] <dednick> larsu: hey. any idea how the accelerators for applicaiton menu item actions are stored in a gmenumodel? it's all done inside gtk shizzle.
[11:12] <dednick> or rather "how it's stored in gactiong"
[11:42] <guest42315> http://blog.qt.io/blog/2015/09/08/qt-5-6-alpha-released/
[12:10] <larsu> dednick: gactiongroup doesn't store them at all
[12:10] <larsu> dednick: they're passed in gmenumodel and gtkapplication adds them for all its windows
[12:22] <greyback> dandrader|afk: hey, would like your opinion on https://code.launchpad.net/~unity-team/qtmir/dpr/+merge/257514 - fact which most bothers me is I needed to pass the dpr value to MirSurface, as the Q*Events are all const. If you've ideas, happy to hear them
[12:25] <greyback> interesting, I've just managed to put my arale into a state where unity8 is getting no input
[12:25] <greyback> I was trying to get a screenshot, and was mashing the vol up/down keys
[12:35] <Saviq> greyback, so bug #1491566 ?
[12:35] <greyback> Saviq: is what I suspect, am trying to debug
[12:36] <Saviq> great, lemme know if I can help
[12:36] <greyback> but the sun has appeared, going for a quick run first!
[12:36] <Saviq> don't let it drain!
[12:36] <Saviq> (arale's battery, that is)
[12:37] <greyback> irish sun has worse battery life
[12:37] <Saviq> :D
[12:39] <davmor2> greyback: I blame Europe they use it all up for hours before it comes to the UK and Ireland
[12:54] <dednick> larsu: ok, i think i found it. thanks
[13:48] <cimi> tsdgeos, is there a silo for the unity-api changes?
[13:48] <cimi> for filters
[13:48] <tsdgeos> i think not
[13:48] <tsdgeos> you have to build the branch yourself
[13:48] <tsdgeos> pstolowski: can you confirm? ↑↑
[13:48] <cimi> that's fine
[13:49] <pstolowski> cimi, there isn't
[13:51] <dandrader> greyback, may I do that later today or tomorrow morning?
[13:54] <greyback> dandrader: no rush at all
[13:54] <mzanetti> dandrader, dednick: anyone of you has time to look into this? https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1493278
[13:55] <dandrader> mzanetti, I could take it tomorrow
[13:55] <dandrader> I think
[13:56] <mzanetti> ok, cool
[13:56] <dednick> be my guest ;) looks terrible