[07:03] <tsdgeos> mzanetti: https://code.launchpad.net/~aacid/unity8/fix_ninja_build/+merge/264383
[08:24] <tsdgeos> mzanetti: actually that it works with make must be just some kind of luck tbh
[08:24] <tsdgeos> it should fail too
[08:24] <mzanetti> tsdgeos, the ninja stuff?
[08:25] <mzanetti> ah... hmm, still... it works with make, so someone will drop this line again (as it happend 3 times already) :D
[08:25] <tsdgeos> mzanetti: yes, because we're just using -lLibraryName
[08:25] <tsdgeos> and hoping it'll be built before
[08:25] <mzanetti> fair enough
[08:25] <tsdgeos> and i guess make is doing some parsing and making sure it happens
[08:26] <tsdgeos> but yes i'll add a comment
[08:56] <tsdgeos> mzanetti: comment added
[08:56] <mzanetti> ta
[10:06] <akiva-thinkpad> Hey anyone home? I was working on the SDK, but have largely finished the project I was working on. I'm looking for some new things to work on, and I have actually wanted to try adding some things into unity8 (desktop mode)
[10:06] <akiva-thinkpad> Just wanted to know where I can get started with this?
[10:08] <akiva-thinkpad> There are two things I want to make sure are added: HUD support for one, and I'd like to make sure thinkpad trackpoints are supported :P This was a big pet peeve of mine in unity7, how the mouse settings were really inaddequate.
[13:51] <MacSlow> greyback_, the qml-scene overlay (for debugging) I can get with QSG_RENDER_DEBUG=render qmlscane foobar.qml, right?
[13:52] <greyback_> MacSlow: for debugging what exactly?
[13:53] <MacSlow> greyback_, so I see the 3D-view of my scene overlayed on top of the qmlscene window
[13:53] <greyback_> MacSlow: QSG_VISUALIZE=overdraw
[13:53] <MacSlow> greyback_, ah that one... thx
[14:53] <seb128> is the app loading screen an unity8 thing?
[14:53] <seb128> or a qtubuntu/mir/... one?
[14:53] <seb128> 1473476
[14:53] <seb128> bug #1473476
[14:53] <seb128> I've a feeling I picked the wrong project ;-)
[15:00] <kgunn> seb128: i don't think it's the wrong thing....
[15:00] <kgunn> greyback_: tsdgeos says this is per design, but surely we should purge the image
[15:00] <kgunn> if an app is closed for any reason
[15:01] <kgunn> otherwise you just have a "random" screenshot w/o context at that point
[15:01] <kgunn> seb128: oh..yeah, could be qtmir maybe
[15:01] <greyback_> kgunn: I guess it depends on if we expect apps to restore to their previous state on startup
[15:01] <greyback_> or will they start up to the default view
[15:02] <kgunn> greyback_:  is there an sdk setting for an app to imply  ?
[15:02] <greyback_> kgunn: no
[15:02] <kgunn> then i don't see how we could guess
[15:02] <greyback_> guess we should ask them if that's even possible with the uitk
[15:03] <tsdgeos> kgunn: we purge it when closing the app
[15:03] <tsdgeos> kgunn: it's just that the app is not closed if you reboot
[15:04] <tsdgeos> greyback_: there is actually a state saver in the sdk yes
[15:04] <tsdgeos> though i really doubt much apps are using it
[15:04] <greyback_> that I know, but can apps tell us if they are using it or not
[15:04] <greyback_> I don't believe so
[15:05] <tsdgeos> ah don't think so no
[15:06] <greyback_> kgunn: we did have design saying if you reboot your phone, the spread should be populated as if you had never rebooted at all...
[15:06] <tsdgeos> right, and the "start with this screenshot" is part of that feature
[15:07] <tsdgeos> months ago was agreed we could land it step by step
[15:07] <kgunn> greyback_: hmmm, but as far as app launch and taking focus, do we _have_ to show that screen shot ?
[15:07] <kgunn> right now it's splash->old ss-> fresh frame
[15:07] <kgunn> could we change to splash-> fresh frame
[15:07] <tsdgeos> kgunn: we don't have to, it was asked
[15:07] <tsdgeos> so we did it
[15:08] <kgunn> ah...so a bad request imho :)
[15:08] <seb128> tsdgeos, kgunn, the design is flawed there and we should tell them
[15:08] <tsdgeos> i disagree, i like it :)
[15:08] <seb128> the "have a switcher with the old state" is fine if apps reopen to that state
[15:08] <seb128> not if they open to something totally different
[15:08] <tsdgeos> then the bug is in the app for not following platform rules
[15:08] <tsdgeos> ^_^
[15:08] <seb128> what are the rules?
[15:09] <tsdgeos> your app can be killed in any moment, the user shouldn't have to care
[15:09] <tsdgeos> so you save your state and restore it on startup
[15:09] <seb128> well that' assuming that you want to restore on start
[15:09] <seb128> like you close settings
[15:10] <seb128> then open the sound panel from an indicator
[15:10] <seb128> it does open to that subpanel which is the right thing to do
[15:10] <tsdgeos> correct
[15:10] <tsdgeos> you closed the app
[15:10] <tsdgeos> there's no state to restore
[15:10] <seb128> well the oom did for you
[15:10] <seb128> open settings
[15:10] <seb128> switch to something else
[15:10] <tsdgeos> ah, i see what you mean
[15:11] <tsdgeos> sure the user just sees the app unfreeze and go to the other page
[15:11] <tsdgeos> as it would have done
[15:11] <tsdgeos> if it wasn't killed in between
[15:11] <seb128> hum, fair enough
[15:12] <seb128> I think we have buggy cases though
[15:12] <tsdgeos> probably
[15:12] <seb128> like webapps not been seen as different apps
[15:12] <tsdgeos> also kgun sayd  splash->old ss-> fresh frame it should just be  old ss-> fresh frame
[15:12] <seb128> right
[15:12] <tsdgeos> it was last when i tried, but maybe it regressed somehow
[15:13] <tsdgeos> seb128: webapps are not seen as different apps? wops, that's bad :/
[15:23] <dandrader> mzanetti, ready for review: https://code.launchpad.net/~dandrader/unity8/phone-lock-landscape/+merge/264300
[15:27] <mzanetti> dandrader, thanks
[19:59] <om26er> mzanetti, Hi! I am having issues with unit8, when autopilot restarts it, it opens in windowed mode, causing my tests to fail
[19:59] <om26er> is there a way to force unity8 to *not* open in windowed mode ?
[20:00] <balloons> om26er, this sounds like the creating a mouse bug
[20:00] <mzanetti> om26er, there's a fix in autopilot on the way, but for now, use "gsettings set com.canonical.Unit8 usage-mode Staged"
[20:01] <mzanetti> balloons, yep, that's the one. actually current autopilot simulates a touchpad :)
[20:01] <balloons> ;-)
[20:02] <om26er> mzanetti, balloons thanks, broke my device, right now, will check once I reflash it
[20:03] <mzanetti> hmm... I wonder why om26er still has the problem, yet I can't find a silo for the fix.
[20:03] <mzanetti> balloons, do you know if it only landed to wily?
[20:05] <balloons> mzanetti, nothing has landed in distro
[20:06] <balloons> but they did push it to the overlay ppa, only for vivid
[20:09] <om26er> mzanetti, I am on wily
[20:11] <balloons> here's the bug: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1471598
[20:12] <balloons> om26er, presumably https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-034/+build/7630756/+files/python3-autopilot_1.5.1%2B15.04.20150708-0ubuntu1_all.deb will fix it for you.
[20:12] <om26er> balloons, thanks
[21:05] <mzanetti> dandrader, yay! qmltest are coming back
[21:05] <mzanetti> not sure if today still, but at latest on monday we should have then
[21:05] <mzanetti> 5 new failures slipped in
[21:06] <dandrader> mzanetti, awesome!