=== mmrazik is now known as mmrazik|afk === mmrazik|afk is now known as mmrazik [07:33] Saviq: good morning [07:33] mzanetti, o/ [07:33] Saviq: hey... take the phone and turn on the screen [07:34] then start dragging the greeter, but don't release [07:34] drag left and right continuosly [07:35] mzanetti, gets stuck [07:35] mzanetti, probably when you reach the DirectionalDragArea [07:35] :/ [07:39] hmm no [07:39] unrelated to the DDA [07:40] Saviq: sorry... had my weekly QA sync meeting [07:40] mzanetti, don't be [07:40] Saviq: soo... yes. [07:40] it freezes [07:40] and actually it happens to me (as I started dogfooding) like every 20th unlock of the phone or so [07:40] and I have to plug it and restart the shell [07:41] I have taken out all the greeter content... still happens [07:41] I have also removed the animation from the background (fade in from behind), still happens [07:42] it kinda seems as when causing too fast dragging at some point the input gets lost [07:42] as the indicator icons still change state (e.g. wifi signal strength) [07:42] Saviq: ^ [07:42] mzanetti, yeah, seems the Revealer gets confused [07:42] or the whole input stack, even [07:43] that'd be bas [07:43] bad [07:43] hi guys [07:43] morning greyback [07:43] hey ho greyback [07:43] greyback: one for you too: [07:44] greyback: start an app [07:44] greyback: restart the shell [07:44] Saviq: mzanetti: greetings on this fine morning [07:44] greyback: try to open a new app [07:44] mzanetti: with trunk? [07:44] greyback: or image 147 (aka. the dogfooding one) [07:45] * greyback gets downloading image 147 [07:52] mzanetti, it doesn't even feel like speed is a factor [07:52] Saviq: hmm... in my experience slow is worse than fast [07:52] mzanetti, yeah I meant it happens in both cases [07:53] mzanetti, it feels like some buffer overflows or something [07:53] Saviq: I have debugged it for a little while on the weekend but didn't really come to anything useful tbh [07:57] mzanetti, the Revealer itself seems fine, tst_Revealer.qml doesn't show the issue [07:59] mzanetti, and dropping the DirectionalDragArea doesn't help, either [08:00] Saviq: the DDA is not used when unlocking yet, is it? I think only the launcher uses it yet [08:00] mzanetti, yeah, I was just afraid the interaction between them was the issue [08:00] Saviq: btw, side note: pmcgowan complained quite a bit about the DDA in the Launhcer on friday [08:00] mzanetti, i.e. the fact that we've added the DDA at all [08:01] mzanetti, what about? [08:02] Saviq: I guess he holds the device in the right hand, starts with the thum at the left lower corner and moves it in a sort of circular gesture towards the upper right (hope you understand what I mean) [08:02] Saviq: his finger always leaves the allowed angle and the launcher gets stuck [08:02] mzanetti, possible, we simply need to tweak the values [08:02] Saviq: sergiusens on the other side really loves the current angle config [08:05] mzanetti, I'm almost sure something overflows, it feels like you need to generate almost exactly the same amount of events to trigger this [08:05] not that that feeling helps much [08:05] haha [08:06] mzanetti, i.e. on manta I need to go back and forth 7-8 times to the center of the screen and back to the right edge [08:07] hmm... could be, yes... what I don't really understand is that it happens only with the greeter. revealing an app from the right edge doesn't have this problem [08:07] but still when removing all the greeter content and replacing it with a black rectangle, it still happens [08:08] mzanetti, I feel like it's the Revealer at fault [08:08] mzanetti, at least the way the Greeter uses it must be exposing some issue in it [08:09] mzanetti, it's quite a complicated beast [08:09] the revealer? [08:09] mzanetti, Revealer.qml [08:10] * mzanetti hammers prints into every line of revealer.qml [08:10] mzanetti, oh, but it also gets stuck after 10 or so times being unlocked :/ [08:10] that's bad [08:11] that's what you meant that it happens for you during normal usage [08:11] yeah [08:11] I wonder why noone else dogfooding encountered that [08:11] Saviq: and then I restart the shell and get hit by the bug I reported to greyback... then I have to reboot :D [08:11] Saviq: so far everyone I told could reproduce [08:12] mzanetti, yeah [08:12] Saviq: and M. Frey said he suffered from that too since a while already [08:12] mzanetti, /me wonders if the buffer "drains" after time [08:12] so if you only do it every minute or so [08:12] it wouldn't happen [08:12] but it doesn't feel so from your experience [08:14] yep, 13 unlocks and now I cannot unlock [08:14] fresh flash [08:14] is bad [08:14] can't bring out the launcher either [08:15] * Saviq wonders if the IFA is animated too often [08:15] that's a new thing [08:17] greyback, mzanetti got it [08:18] really? [08:18] \o/ [08:18] :) [08:18] mzanetti, drop the InputFilterArea from Greeter [08:18] * mzanetti pimps his dogfood [08:21] wth just happened... [08:21] is it just me or has compiz just become freakishly unstable? [08:22] become? [08:22] yeah... removing IFA gets around it indeed. [08:30] mzanetti: when you say "restart the shell" - how are you doing that? [08:31] greyback: usually I do a "sudo service ubuntu-session restart" [08:31] mzanetti, greyback https://code.launchpad.net/~saviq/unity/phablet.fix-greeter-stuck/+merge/167002 [08:31] mzanetti: I see. Usually when I do that it kills the applications too, but sometimes qmlscene doesn't respect that [08:32] Saviq: btw... afaik starting today autolanding etc will be moved over to saucy. we are supposed to backport ciritical fixes to the dogfood image manually [08:32] greyback, it won't kill the apps if they're not focused (i.e. stopped) [08:32] Saviq: ah really [08:32] greyback, yeah, as SIGINT doesn't do anything to them [08:33] they need SIGKILL [08:33] SIGTERM, rather [08:33] (doesn't do anything) [08:33] makes sense [08:34] Saviq: can you explain why this actually fixes it? [08:34] mzanetti, the InputFilterArea doesn't update its size all the time to match with the Greeter's [08:34] mzanetti, so there's no updates sent to the input stack [08:35] mzanetti, and that's what was getting stuck, I believe [08:35] Saviq: oh... I see.... didn't know the greeter is resized [08:35] mzanetti, it's not [08:35] mzanetti, but it's moved around [08:35] mzanetti, i.e. geometry changes [08:35] Saviq: ah ok... [08:35] yeah... might wel be.. [08:35] mzanetti, still needs fixing at the other side [08:35] Saviq: so in that case the actual bug must be inside the IFA [08:35] mzanetti, yes [08:36] mzanetti, but anyway we need to review our use of IFAs to not animate them, it usually is the case of "should we filter this area or not" [08:36] +1 [08:36] mzanetti, regardless of how far the related gesture is [08:36] should almost be an on/off thing really IMO [08:37] yeah, I agree... thats what I do in the launcher... [08:37] greyback, well, there's probably a few cases: the left / top / right edge [08:37] is >0 pixels shown, enable it fullscreen [08:37] greyback, and then the whole screen [08:37] Saviq: hence the "almost" :) [08:37] yup [08:37] and yeah, the launcher [08:37] and the hud [08:38] so yeah, there's a few, but they should have static geometry [08:42] mzanetti: so restarting shell, the bug I see is that the apps lens has a black preview of an app that didn't die. I can still launch apps however, and window switching is ok. What am I missing? [08:42] greyback: my scenario: [08:42] I launcher the phone app [08:42] I launch another app [08:43] bring the phone app to top (app screenshot gets taken) [08:43] restart the shell [08:43] start the gallery, once its loaded, it shows the app screenshot of the phone (you can see the gallery starting up an initializing, but then overridden by the phone app screenshot) [08:44] Saviq: approved your fix... once this and and the app screenshot fix (^) is in, I vote for a new release as those are the only 2 issues I found while dogfooding through the weekend [08:45] mzanetti, yeah, will do [08:46] Hmm, another bug: open phone app at the dialer screen, left-edge swipe to show launcher - rest of screen is darkened a bit, tap a number on the dialer. Dialer gets that input event, but it shouldn't [08:46] mzanetti, we might also think about increasing the angle on the Launcher [08:46] mzanetti, will ping pmcgowan about this later [08:46] Saviq: yeah.. I increased it to 30 in my branch.. seems perfect for me... I wanted to ask Pat how he feels with 30° [08:47] its 10° right now [08:47] yeah, probably too low [08:48] Saviq: btw... I think my launcher branch improves the overall behavior quite a bit.. might make sense if you guys start testing it [08:48] mzanetti, yeah, will do [08:49] I'll push the 30 degrees there [08:51] Saviq: btw... xbmcremote should be in a usable state (in case you wanna start dogfooding too ;) [08:51] :) [09:01] mzanetti: I'm really struggling to reproduce your bug. Worst I see is a flicker of the last-focused-app when launching a new app (not good tho, will look into it) [09:02] fook... with every letter I type into the dash, a Chromium tab is opened [09:05] oO [09:05] that's insane [09:05] ghost in the machine? [09:06] greyback, probably some scope gets confused [09:07] confused or not, no scope should be able to do anything like that [09:09] greyback, actually it's the online accounts [09:10] greyback, it had (has?) problems with accessing my google account, so signon-ui did something weird [09:11] Saviq: very very weird [09:11] greyback: ok... I only can reproduce it in combination of the greeter bug [09:11] greyback: so open an app, say the phone-app [09:12] greyback: lock the screen, and then reproduce the hang by swiping the greeter left/right continuously [09:12] greyback: it'll get stuck, then reboot the shell and try starting another app [09:12] don't ask me how that is related... [09:13] Ok, will try. But code-wise, before /every/ animation we request a new screenshot. They are cached however, so maybe there's a cache bug. Will see [09:13] thanks for digging for me [09:14] greyback: are you doing something when the animation is finished too? [09:14] greyback: so maybe its only when restarting the shell in the middle of an animation [09:14] mardy, ping [09:14] mzanetti: nope, nothing fancy on animation finish. Just hide the screenshot [09:15] but we always refresh screenshot before starting a new animation [09:15] greyback: weird thing is, while an animation is running I can see the screenshot of the correct up. only when it then sits there and should run (e.g. no screenshot at all) I see the screenshot of the app from before the restart [09:16] s/up/app/ [09:22] mzanetti, I think it might be not a screenshot, but the actual app [09:23] mzanetti, while the new app is painting its first frame [09:44] Saviq: should I create a new directory test/qttest/ in unity-api? [09:49] mzanetti: hmm, while I've still not found your exact bug, I've found something quite likely related. At least it's somewhere to start [09:49] Saviq, I think the infographics are ready to land now. Mind giving me and updated opinion? [09:51] Saviq, just noticed one more bug I'll chat to pete-woods about it, will get back to you when it's sorted. [09:52] sil2100: ping [10:00] Saviq, apparently it's cool. As above if you wouldn't mind having another look at it. [10:00] mzanetti, yes please [10:01] nic-doffay, mzanetti was doing your review there, so I'll let him take care of it :) [10:01] ack [10:01] mzanetti, hold off on that... Merging trunk overwrote something. [10:09] Saviq: pong [10:09] mardy, hey, it seems signon-ui has some issues with the Ubuntu-SSO enabled Google accounts [10:09] mardy, at some point every letter entered into the dash opened a tab in Chromium for me... [10:10] Saviq: what did the tabs contain? [10:10] mardy, about:blank... [10:11] weeeird [10:11] mardy, resolved now after a few runs of "give access" in signon-ui, but just letting you know that there are some issues like that [10:11] Saviq: I'll check, thanks [10:11] mardy, weird indeed, imagine how I felt ;) [10:13] mzanetti, lol [10:14] Doing one last commit for new gradients. [10:25] mzanetti, it's ready whenever you are. Shouldn't be a lot left to look at. [10:30] nic-doffay: hehe... go into your builddir and do a "make testGreeter". Seems the infographics has troubles keeping the pace :) [10:30] mzanetti, argh forgot about the tests. [10:31] nic-doffay: you're lucky... till all passing. however, I miss a test that actually waits for the animation to be completed and checks if everything is fine [10:31] nic-doffay: do you think that would be worth having? [10:33] mzanetti, elaborate on everything fine :P [10:34] nic-doffay: the animation actually stops and all the final values have been reached [10:34] nic-doffay: and it seems you messed up with the last merge. you reverted the change from mterry that changes the PathView to be a ListView [10:35] mzanetti, I'll revert back to his revision. [10:37] nic-doffay: the rest seems ok to me... fix that merge and we can merge it I'd say [10:38] mzanetti, any idea what's going on with the tests? [10:38] nic-doffay: ? [10:38] whats wrong with them? [10:39] getting errors trying to make them. [10:39] mzanetti, ^ [10:39] nic-doffay: works fine for me [10:40] nic-doffay: if the error is "cannot load libunity-core-0.6.so.5" or something like that, wipe your unity_build directory and do a fresh ./build -s [10:40] I had that end of last week [10:40] cool === mmrazik is now known as mmrazik|afk [11:09] in qml, how do I write a timer to update a variable at midnight? [11:11] not sure I can change the interval while running... [11:11] Cimi, ATM you'd need a timer to check every minute if midnight passed [11:12] Saviq, updating the interval? [11:12] Saviq, when you start the calender, it's as long as the remaining time till midnight [11:13] Saviq, then you trigger it and set interval of one day [11:14] Cimi, that's complicating too much, we'll later have an object that you will ask for signals with given resolution [11:14] ok [11:14] Saviq, I'm sick btw :) [11:14] Cimi, and why're you happy about that? ;) [11:15] Saviq, not happy :) [11:15] Saviq, but better to mile than being sad, always [11:22] mzanetti, is it literally only the PathView that needs to be changed back to a ListView? [11:23] nic-doffay: no... I think mterry's commit did a few other small graphical changes too [11:24] Saviq: question: unity-apis will generate a library we can link at some point, right? [11:24] mzanetti, is that revision 656? [11:26] nic-doffay: don't think so [11:27] nic-doffay: oh shit... it reverts more [11:27] nic-doffay: also the fix that we have only 50 people in the lens [11:28] mzanetti, which revision screwed everything? [11:29] nic-doffay: I guess your last merge [11:29] nic-doffay: the changes you reverted came in friday afternoon... so you messed up either friday night or today morning [11:30] mzanetti, not sure about that, at least for the abstract headers I really just planned to include them as sources in the implementation [11:31] Saviq: so the actual question is, if I create a mock implementation with some launcher entries now, how will I be able to use that in the shell until the real one is done? === MacSlow is now known as MacSlow|lunch [11:32] mzanetti, a plugin on the same path should be enough? [11:32] Saviq: plugin? [11:33] mzanetti, your case might be slightly different [11:33] Saviq: so it is a lib in the end... [11:34] mzanetti, for Notifications what we have is a mock implementation (a Unity.Notifications plugin) inside lp:unity-api [11:34] mzanetti, but that's just minimal, one that's used to pass the tests inside lp:unity-api [11:35] Saviq: right... but in that case you don't need the header and as long as there is a plugin with that name somewhere it'll work [11:35] mzanetti, yeah, the header is just convenience [11:35] Saviq: in my case I need to include a header and then still someone needs to load the actual backend and give me a pointer to it somehow [11:37] mzanetti, easiest solution would be to have a separate "Launcher backend" plugin, one that will expose the list of favourites, and that we can pass to our internal launcher model [11:39] Saviq: the plugin interface is then in the unity-api repo or in ours? [11:39] mzanetti, I'm starting to think the separation between "our part of the backend" and "their part of the backend" becomes difficult [11:42] mzanetti, there should be just one "Unity.Launcher" plugin that does everything what we need - and the shell-facing interface would just be model, with a way to pass the list of running apps to it [11:43] Saviq: hehe... thats what we asked you in the meeting last week [11:43] mzanetti, I misunderstood the question, then :/ [11:43] mzanetti, I don't see a reason to split it up unnecessarily [11:44] Saviq: nah... I think its fine right now... the question is just how to load the backend implementation from with in c++ [11:44] mzanetti, I don't think we need to, we just need to pass the list of favorites to the "launcher model" [11:45] mzanetti, this way we'll be able to qml-test it easily, too [11:46] mzanetti, i.e. Launcher.Model { favourites: Launcher.favorites; running: Mir.runningApps } [11:46] Saviq: so you mean the launchermodel I have in my launcher branch should be moved over to unity-apis? [11:46] mzanetti, not the implementation of it, just the interface definition, with the abstract headers === pete-woods is now known as pete-woods-lunch [11:47] Saviq: huh? I don't see what that would change [11:47] mzanetti, mumble? [11:47] yeah [11:57] pstolowski: pong! [11:58] sil2100: heyah! how does the landing story look today? [11:59] pstolowski: I just finished all the irritating tax errands so I can start soon [11:59] pstolowski: we'll need to disable 2 scopes though, the 2 python2 ones (launchpad and sshsearch) [12:00] sil2100: you will have a libunity update to do for that I guess ^ [12:00] (and rebuilding libunity and then unity) [12:00] pstolowski: we can still land them in universe though [12:00] didrocks: what's wrong with them? [12:00] pstolowski: we are moving away from python2 installed by default [12:00] so we don't want to introduce back python2 deps [12:01] didrocks: ah, fair enough [12:01] didrocks: will let davidcalle know.. [12:01] pstolowski: thanks, I was hunting for him, but not around :p [12:02] Ah, so the decision is 'no' to those scopes in the end [12:02] yep :) [12:02] sil2100: pstolowski: I'll let you handle the 2 rebuilds? [12:05] didrocks: I'm unclear on what that means and what needs updating in libunity? [12:05] didrocks: same here - do you mean getting rid of python2 deps? [12:06] In libunity? [12:06] pstolowski, client-scope.json [12:06] scopes* [12:06] mhr3: right.. [12:06] oh [12:06] mhr3: someone following, thanks! :) [12:06] so updating this one [12:07] mhr3: thanks, forgot about that one [12:07] and have unity rebuilt to pick the recommends frmo the new .json file [12:07] pstolowski: can you scratch out a MR? [12:07] sil2100: y [12:07] Thanks! I'll approve it when needed [12:15] davidcalle: hi! [12:19] pstolowski, hey :) [12:19] back, had power outage [12:20] davidcalle: (13:59:53) didrocks: pstolowski: we'll need to disable 2 scopes though, the 2 python2 ones (launchpad and sshsearch) [12:20] davidcalle: (14:00:23) didrocks: pstolowski: we can still land them in universe though [12:20] davidcalle: (14:00:48) didrocks: pstolowski: we are moving away from python2 installed by default [12:21] pstolowski, thanks for the heads up. Universe is ok until their deps move to python3 (or maybe Launchpad could end up server side). [12:23] davidcalle: https://code.launchpad.net/~stolowski/libunity/disable-some-scopes/+merge/167027 [12:23] sil2100: ^ [12:24] pstolowski: you should bump debian/changelog version so that unity can build-dep on it [12:24] sil2100: ^ [12:25] didrocks: k === mmrazik|afk is now known as mmrazik [12:34] didrocks: just making sure, a bump to 7.0.0daily13.05.31ubuntu.unity.next-0ubuntu2 is ok, right? It certainly doesn't look beautiful when dep'ing such a version, but should be ok? [12:35] sil2100: should rather be 7.0.1 IMHO but that's fine as well [12:36] sil2100: hum, look at what's in the ppa [12:36] sil2100: but I guess the version is higher than 7.0.0daily13.05.31ubuntu.unity.next-0ubuntu2 [12:36] mzanetti: I've replied to a couple of your comments, can I get your input please https://code.launchpad.net/~gerboland/unity/refactor-wm-and-test/+merge/166524 [12:37] didrocks: I was wondering about bumping the micro version, but we're not really breaking the API here... [12:39] sil2100: micro version is not for breaking the API, it's more for adding a new capability that you depend on, which is the case here, you want to pick the latest :) [12:40] didrocks: that's not what the example in the FAQ shows! ;) [12:40] sil2100: it's a wiki, feel free to edit it to amend it :) [12:42] pstolowski: so, as I discussed with didrocks, change the version number to 7.0.1-0ubuntu1 if you can (and in configure.ac bump the version as well) [12:43] pstolowski: this way it'll be indeed cleaner in the unity dependencies [12:43] greyback: answered [12:43] mzanetti: thanks [12:44] mzanetti: ok I see the value, I'll add it. Shouldn't take too long === alan_g is now known as alan_g|lunch === MacSlow|lunch is now known as MacSlow [12:51] Saviq: ok. now I don't see any more why I would need anything in unity-apis at all for the launcher... I would just move that header file into lp:unity/phablet and we implement all stuff in there [12:51] mzanetti, thing is, ultimately we don't want the Unity.Launcher plugin to live with lp:unity/phablet [12:52] oh... I see [12:52] mzanetti, because we want to allow different implementations of it [12:52] mzanetti, hence the need for lp:unity-api at all - a way to maintain a contract between the shell and $implementation [12:53] mzanetti, i.e. the shell is supposed to be a dumb View on top of the data coming from Unity.Launcher [12:53] mzanetti, and whoever implements Unity.Launcher needs to adhere to that contract [12:53] mzanetti, hence the split [12:53] didrocks: to get the unity libunity version bump in, I will have to first run the re-build for libunity alone, right? Since otherwise the merger won't find 7.0.1 and will bail out - the other way would be merging it in manually and re-running both libunity and unity at once [12:53] mzanetti, you can live without it of course [12:54] mzanetti, but you'll just have more work ahead of you [12:54] sil2100: exactly [12:54] and by you I mean $someone who implements the Unity.Launcher plugin [12:54] mzanetti, ^ [12:55] sil2100: as you wish, check with upstream but personnally, I'm fine with a manual push to speed this up (on the unity side) [12:55] Saviq: ok... but that header that I have in there right now doesn't make any sense in there [12:55] mzanetti, /me looks [12:56] Saviq: thats basically the interface between me an Wellark [12:56] and [12:56] mzanetti, yeah [12:56] mzanetti, that's not supposed to be there [12:57] ok... so for now I just put that into lp:unity/phablet and create the other interface in the unity-apis. we can start with the implementation in unity/phablet until we know where it should go for real [12:57] Saviq: ^ [12:57] mzanetti, yeah, we can just extract the API parts later [12:58] mzanetti, but yeah, just go with a simple implementation now [12:58] mzanetti, simply because it will probably change substantially as we go [12:58] mzanetti, and at the end when we decide it's ready to ship, we extract it [12:59] mzanetti, and start enforcing the contract [13:02] mzanetti, sorry if I got you confused [13:03] you kinda did :D no worries tho. [13:05] Saviq just 2 cents....we should probably enforce few weeks before Oct [13:05] just as a test to see if we're settled [13:06] kgunn, way before that :) [13:06] if api's still changing...that'd be troubling [13:06] lol === pete-woods-lunch is now known as pete-woods [13:06] Saviq cool....wasn't sure what you meant by "ready to ship" [13:06] bregma: ping! [13:06] kgunn, "when we decide it's ready to be enforced" more or less :) [13:06] kgunn: if it compiles, ship it [13:07] kgunn, so "when it works" more or less [13:07] Saviq mzanetti cool [13:08] Saviq mzanetti as long as "when it works" is prior to Oct minus 3 weeks ; ) [13:08] right ;) [13:09] kgunn, any more info on the next task for me or should I just shout at Loic? [13:10] sil2100, pong [13:11] nic-doffay ping loic he was ready when you are [13:11] Saviq ^ nic-doffay gonna tackle openeffect [13:11] kgunn, yup, great, thanks [13:12] bregma: we're modifying he list of scopes in libunity and bumping the version of libunity, we'll also need to bump the dep in unity [13:13] bregma: would you mind if I would merge in manually https://code.launchpad.net/~sil2100/unity/bump_libunity_for_scopes/+merge/167031 once the libunity version bump is in? [13:13] bregma: since otherwise the merger won't let the merge in, because we would have to release the libunity new version first [13:13] But with a manual merge, we can do both at once [13:14] sil2100, unity 7.0.1 would be a raring SRU release [13:14] I think you would want to prepare a 7.1.0 release [13:15] bregma: I mean libunity 7.0.1 [13:16] bregma: since from what I see saucy has 7.0.0 with the 100scopes right now... is that incorrect? [13:16] ah, OK, I misread the merge [13:16] * bregma rubs his eyes again [13:20] bregma: once this merge (for libunity) gets in [1], I would like to merge manually the branch I pasted earlier [13:20] [1] https://code.launchpad.net/~stolowski/libunity/disable-some-scopes/+merge/167027 [13:25] tedg: so, we have maybe found the source of the hang in dbus and the whole machine [13:25] mhr3: ^ [13:25] ? [13:25] mzanetti: Saviq I do, less randomness going on! I'd really like some histerisys for bringing up the launcher too :-) [13:25] hud-service is using 2.2g [13:25] so the machine is swapping [13:25] and dying [13:25] sil2100: ^ [13:25] didrocks, wooooo [13:25] didrocks, Ah, on Unity 7? [13:25] sergiusens: what are you talking about? [13:25] tedg: right [13:26] didrocks, Yeah. I've got a fix on the TODO list for that. [13:26] didrocks, Queries aren't getting free'd in HUD. [13:26] sergiusens: ah... the revealing angle [13:26] tedg: can it get higher on the stack? It's blocking us for more than a month ;) [13:26] mzanetti: yeah, that :-) [13:27] didrocks, Oh, I didn't realize. I figured it wasn't a big deal because for most people HUD dies in 10 min anyway. [13:27] didrocks, can't we just kill hud before each AP invocation for now? [13:27] ! [13:27] tedg: or add a segfault please :p [13:27] sergiusens: could you try with 30 degrees angle if you still like it? [13:27]