[00:02] oh [00:02] ahayzen_: I put them on different tabs [00:03] ahoneybun, awesome :) you should be able to make that component generic as well [00:04] ...if it is exactly the same on both tabs [00:06] ahayzen_: my friend was saying that the app I am coping from iOS has a button that switch the buttons to edit the other textfield [00:07] you could do that [00:07] oh? [00:08] that would be ideal [00:08] just have a property TextField focusedField ... then set it to the one that the buttons are focussing on ... like you mean that both text fields are visible? you have a button to flip which the buttons write to? [00:09] yea [00:09] yeah do that ^^ [00:09] let me grab a screeni [00:09] then have a button at the bottom to flip that has... onClicked: focussedField = focussedField == fieldA ? fieldB : fieldA [00:10] then change when you click the number buttons to reference focussedField.text [00:10] ahayzen_: too much at once lol [00:11] hah [00:11] not even to the property yet [00:11] lol [00:12] so like put the property somewhere where the buttons can access it...so like in the Column {} [00:12] https://plus.google.com/+AaronHoneycutt/posts/jA63bs8DkCp?pid=6129216980386487874&oid=110525358571541799848 [00:13] so what changes the focus of the buttons? [00:13] there is a button above the numbers [00:14] each number [00:14] ok i think what i said will work [00:17] so a property [00:17] so basically have a property storing the currently focussed textfield [00:17] 2 buttons will switch the numbers button to effect each textfield [00:18] yea [00:18] then you have a button(s) that flip that value [00:18] property TextField focusedField [00:18] ? [00:18] yup [00:18] I would like a example if you could [00:18] and maybe set it to the left one to start with [00:18] I learn like that [00:18] erm gimme like 15min+ i gotta collect washing :) \o/ [00:19] property TextField focusedField = score1.text? [00:19] * ahayzen_ learns by example as well ;) [00:19] property TextField focusedField = score1 ... was what i was thinking [00:19] http://pastebin.ubuntu.com/10656622/ [00:19] k [00:20] outside of anchors {} ;) [00:20] i'll build something in a bit ;) [00:20] brb [00:21] k === chriadam|away is now known as chriadam [00:42] ahoneybun, something like this ? http://pastebin.ubuntu.com/10656754/ [00:43] or like you could use states if you started having more things depend on the currently focused field [01:25] whats the add 1? [01:25] oh [01:26] a label lol [01:27] ahoneybun, is that the sortof thing you were looking for? === daz is now known as Guest74681 [01:27] let me try [01:29] from this example the buttons should not have ids === Guest74681 is now known as dazza5000 [01:30] ahayzen_: TypeError: Cannot read property 'text' of undefined [01:30] ahoneybun, is that in mine or your code lol ? [01:30] mine [01:31] I replaced mine with ideas from yours [01:31] ahoneybun, you probably haven't set an initial value for the focused field? [01:31] ahayzen_: http://pastebin.ubuntu.com/10656994/ [01:31] ahoneybun, ah parent.focused won't work [01:32] yea [01:32] it would either be parent.parent.focused.text or put an id on the column and do ... columnId.focused.text [01:32] ..or it might by inscope anyway so you can do focused.text [01:32] one of them will work ;) [01:33] ok parent.parent works [01:33] now the button [01:34] ahayzen_: it works! [01:34] \o/ [01:34] brb bathroom and sode [01:34] *soda [01:34] * ahayzen_ is likely to go to sleep [01:37] back [01:37] now to add a + and - buttons [01:39] \o/ [01:40] can I have the 1 2 3 and so on buttons switch from adding to sub? [01:41] adding to sub? [01:41] + to - [01:41] turn it from adding 1 to taking 1 away [01:42] well it is appending it to a string [01:42] but like you could take the substring of it [01:42] oh? [01:42] depends if you actually want them to act like push/popping from a string ... or like adding/subtracting from an integer? [01:43] 2nd one [01:44] you'll need todo parseInt each time you want to manipulate the value then ... or have another property that stores the actual value as an int and then the textfield just 'views' that [01:46] way above me [01:46] hah [01:48] parseint? [01:48] yeah https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt?redirectlocale=en-US&redirectslug=JavaScript%2FReference%2FGlobal_Objects%2FparseInt [01:48] and then toString() but that could get messy [01:48] oh [01:49] it may be best to have a property inside the textfield with the actual value ... or to use a control that allows you to use ints rather than strings [01:49] how would the property go? [01:49] property int actualValue: 0 [01:49] then do text: actualValue.toString() [01:49] ..i think... [01:50] then you would be able to do parent.parent.focused.actualValue += 1 ... or -= 1 [01:50] would the property be below the other one? [01:50] would need one inside each TextField [01:50] but then the type of the other property may need to change to var rather than TextField as well lol [01:51] oh boy/ [01:51] lol [01:51] property inside the textfield {} ? [01:51] yup [01:52] { property} [01:52] hm? [01:52] like TextField { property int actualValue: 0 } [01:53] and then text: actualValue.toString() as well [01:53] k [01:53] for the buttons? [01:53] textfield? [01:54] the buttons need to have their parent.parent.focused.text changed to parent.parent.focused.actualValue [01:56] ok [02:00] how do I switch the buttons from + to - ? [02:00] heh [02:01] have another var ... which you set to 1 or -1 ... then do ... actualValue += 8 * myVar ... so it would do += 8 * 1 .... or += 8 * -1 [02:02] (for the button for 8 ;) ) [02:02] ahayzen_: var? [02:02] property [02:02] property var [02:02] property int [02:02] or var would work as that can be anything [02:03] some many "..." lol [02:03] it makes it hard to read [02:03] http://doc.qt.io/qt-5/qtqml-typesystem-basictypes.html [02:03] haha [02:03] plus I'm back at C++ or code in gerenel [02:04] ahayzen_: can you write what the 8 button property would look like? [02:04] ok you wan't another property at the column level. which you then set to 1 (for addition) or -1 (for subtraction) [02:05] then your onClicked for the button, say 8, would change to be parent.parent.focused.actualValue += 8 * myProperty [02:05] you may also want to look at the repeater ;) http://doc.qt.io/qt-5/qml-qtquick-repeater.html [02:06] property var myProperty: 1 or -1? [02:07] you would change its value from another set of buttons ;) [02:07] ? [02:08] so have a button to do addition/minus mode? [02:08] I have a button to switch modes [02:09] yeah which then switches the property to be either 1 or -1 [02:09] http://pastebin.ubuntu.com/10657197/ [02:09] I'm working on the 1 button [02:10] yeah like that will by subtracting at the moment? [02:10] so make another button which changes myProperty = 1 then it'll be adding :) [02:11] oh ok [02:11] ahoneybun, anyway mate i've gotta go to sleep now ;) have fun :) [02:11] thanks ahayzen_ alot [02:11] no problem :) [02:11] have some good sleep [02:11] thanks night o/ [02:46] error in uploading click package to ubuntu app store | http://askubuntu.com/q/600107 [03:56] ahoneybun: I am now, if you still need help [03:58] mhall119: ahayzen has been helping a lot with *our* new app [03:58] a scoreboard [03:58] nice, I figured when I saw ahayzen talking to you that you didn't need me anymore :) [03:59] mhall119: I sent a email to the membership board [03:59] \o/ [03:59] always need you mhall119 :) [04:00] :) [04:00] mhall119: http://imgur.com/dxXQE8x [04:02] my app also has 290 users now! [04:03] the beginners app? [04:03] yep [04:03] awesome [04:03] yea [04:04] it was 240 on friday [04:04] then 271 on sat [04:04] now 290 [04:04] is there a official facebook page [04:04] ? [04:05] for what? [04:05] Ubuntu [04:05] in general [04:05] https://www.facebook.com/ubuntulinux [04:06] * ahoneybun needs to make a icon for gazeteer [04:06] thats community managed [04:06] https://www.facebook.com/ubuntuappdev for appdev [04:06] that's our official page [04:06] ok [04:06] I did not want to put a non offical page in my app [04:07] in case someone put some bad stuff on there and hurt the image of ubuntu [04:14] mhall119: I think like 5 or 6 people would vote for more including you for the Board [04:17] * mhall119 is already on a Council [04:19] whats up everyone. [04:19] bzoltan_, or zbenjamin -- ping [04:25] hey akiva-thinkpad [04:25] ahoneybun, o/ whats new? [04:25] akiva-thinkpad: almost 300 users [04:25] lol triple :) [04:25] nice stuff [04:26] yea [04:26] making a new app with ahayzen's help [04:30] mhall119: [04:30] lint_maintainer_domain [04:30] email=aaronhoneycutt@ubuntu.com matches special domain=com.ubuntu.aaronhoneycutt.gazeteer [04:30] ? === ahoneycutt is now known as ahoneybun [04:55] ahoneybun, new app? [04:57] yea [04:57] a score keeper [04:59] ahoneybun, for golf? [05:01] anything really [05:01] it was for a card game [05:01] :) [05:01] but could be used for a lot of things [05:02] akiva-thinkpad: I think it is pretty cool [05:02] I could not find anything like it on the store currently [05:03] ahoneybun, if you have a use for it, then this is reason enough to have it. [05:03] yea [05:04] I just need to get the icon made up [05:13] akiva-thinkpad: still around? [05:13] ahoneybun, yah [05:14] akiva-thinkpad: I'm getting a warning from the SDK [05:14] ? [05:15] let me get it in a pastebin [05:15] email=aaronhoneycutt@ubuntu.com matches special domain=com.ubuntu.ahoneybun.gazeteer [05:19] sounds like something in a json file [05:21] com.ubuntu.ahoneybun.gazeteer [05:21] Aaron Honeycutt [05:21] name and maintainer [05:29] The uploaded package name (com.ubuntu.aaronhoneycutt.gazeteer) does not use your namespace (aaronhoneycutt) [05:38] hmmmm [05:38] don't know; [05:43] I can't upload it till I fix it so.. [05:44] I'll wait till more people are online [05:44] thanks akiva-thinkpad === chihchun_afk is now known as chihchun [07:46] Morning all o/ [07:47] lut davidcalle [07:47] Hey seb128 :) [08:28] popey hello! If you will have some free time, please, test it: https://code.launchpad.net/~mrqtros/ubuntu-rssreader-app/ubuntu-rssreader-app-startup-time/+merge/253769 [08:29] mrqtros: saw that over the weekend, will take a look, sure [08:33] good morning [08:34] hey dholbach [08:35] Hi, dholbach [08:37] hi seb128 [08:37] hi mrqtros [08:37] popey thanks!) Joey will review too, I hope this will be enough) If you will like it, we can update version in the store. I think that it's time to up minor version ;) After transition to C++ we can up major version to 1.0 === dholbach_ is now known as dholbach [09:38] !ping [09:38] pong! [10:08] akiva-thinkpad: hello, what's up [10:09] bzoltan_, on the autopilot plugin; I could not find the widget in the run config to insert my widget into. Its not in the object pool, or a child of anything. I was wondering if I could make it my own mode instead; that would be easier I think. [10:10] does that make sense? [10:11] give it its own mode* [10:11] I don't know why I said "my" [10:12] I made a thread about it in qt center; I didn't get an answer http://www.qtcentre.org/threads/61656-Cant-find-object-for-quot-Mode-Projects-gt-Project-gt-Build-amp-Run-gt-Kit-gt-Run-quot-to-add-widget [10:13] My understanding is that if I wanted to add a configuration widget into the run config of a project, I would need to find the widget to insert my widget into from the object pool. [10:22] akiva-thinkpad: upstream does not want to overload the fancytabbar with new modes. That is only a simple point...maybe not even th emost relevant. [10:22] bzoltan_, does my problem make sense though? [10:23] bzoltan_, the only other way I can figure this, other than coupling it with a different mode, [10:23] akiva-thinkpad: I do not think that the widget what you need is exposed... so I doubt that you can add a new widget there [10:23] bzoltan_, so I would need to push to qtcreator, an addToObjectPool() right? [10:23] akiva-thinkpad: I am out of office today... and zbenjamin is off too, so it is hard to figure out much :) === chriadam is now known as chriadam|away [10:25] bzoltan_, thats fine. I just want to tie up this loose end. Do you think i should see if qtcreator would allow me to push a patch that would expose that widget? [10:25] or should I ask you later when you are in the office? [10:26] akiva-thinkpad: Not a bad idea to check with the upstream [10:26] bzoltan_, okay i'll try that then. enjoy your day off [10:26] akiva-thinkpad: thanks :) [11:12] dpm, I look forward to rtm moving to vivid at some stage, so we can drop the hack for bug 1434415 :) [11:12] bug 1434415 in Ubuntu Help App "Build fails on utopic" [High,In progress] https://launchpad.net/bugs/1434415 [11:13] it'll require all of us hackers to move to vivid too (it's partly not on my radar because I moved to vivid a while ago :)) [11:28] dholbach, huh... I just realized there is no animal background for vivid [11:28] animal wallpaper* [11:29] akiva-thinkpad, you don't want me to fix that [11:29] dholbach, lol [11:29] it'd probably look a lot like http://www.goparoo.com/kids/drawings/anna-africa-monkey.gif [12:11] ping nik90 (dekko on lxc question) === _salem is now known as salem_ === salem_ is now known as _salem [12:41] daker: pong [12:42] nik90: do you know how can i run dekko on lxc ? [12:42] dekko doesn't run on 14.04 [12:42] daker: Have you got the ubuntu-sdk libs installed on lxc? Or do you need help with that as well? [12:42] yes [12:42] from A-Z [12:43] daker: http://nik90.com/fiddling-around-with-lxc-containers/ [12:43] daker: ^^ should help with getting lxc up and ready from scratch on 14.04 [12:43] So I see https://code.launchpad.net/~dholbach/help-app/1434125/+merge/253658 is still a thing dholbach :-) [12:44] nik90: ok i'll try it [12:44] daker: once you get lxc up and running, you should be able to open a lxc terminal and run the cmake scripts for dekko like you always do [12:45] daker: the only drawback of lxc is that it doesn't allow creating chroots that one might need to run dekko on the phone. But I guess that time you can always use the host machine for that [12:46] balloons, yes - didn't ahve time over the WE [12:46] nik90: no i don't need a chroot, i only want to run dekko on desktop so i can fix/test stuff [12:51] bzoltan_: hi! Do you have a minute to talk about bug 1393697? [12:51] bug 1393697 in click (Ubuntu) "Cross qmake to the chroots" [High,Confirmed] https://launchpad.net/bugs/1393697 [12:52] mardy: that issue is long fixed [12:53] daker: ok [12:54] mardy: but keep in mind that it is available only for Vivid. because it needed a qtbase update what was hardly possible for Utopic. [12:55] nik90, it would be nice if the handle of the circle menu could drop a slight shadow ... i'm using my webapp hack wih all my webapps locally and notice that on white pages the handle kind of vanishes visually [12:55] bzoltan_: right, so, do I understand correctly that this does not depend on which Ubuntu version the developer is using, but it depends only on the targetted framework? [12:55] bzoltan_: I'm using vivid, but my click framework is 14.10 [12:55] mardy: Yes [12:56] contacts app shows blank page when tapping on "Import contacts via Google" but the phone is not connected [12:56] bzoltan_: not even if we pay Mirv a beer? ;-) [12:57] mardy: we need to offer something harder to him and to a bunh of other folks :) [12:57] which folks do you want to offer to Mirv ? === rickspencer3_ is now known as rickspencer3 [12:57] ogra_: funny one :-) [12:58] bzoltan_: is it only about qtbase, or would there need other packages to be updated (click, I guess)? [12:58] "only" :-) [13:02] mardy: backporting the new qtbase to 14.10/rtm is probably not something you want to have done :) [13:05] qt 5.4 comes to rtm by making vivid the rtm :) [13:06] yeah taht [13:06] so "just" fix all the vivid bugs [13:07] mardy: qtbase can't be updated alone, it needs to be all 20 Qt modules plus rebuilds of various components of ours (which means backporting qt 5.4 related fixes from trunks) [13:07] mardy: qtbase and click, that is all [13:08] but speaking about backporting, if someone can pinpoint the needed feature from 5.4 code commits and it can be backported to 5.3, that would be possible and would only affect qtbase [13:08] mardy: for the sdk... and as Mirv sai, all other package what is built on qtbase should be rebuilt... joyride [13:09] oh right now reading backlog, cross qmake package would probably be doable by just updating qtbase, unless there was something 5.4 specific in there. [13:10] Mirv: but that would still break the framework [13:11] ok [13:11] Mirv: because building against qtbase 5.4 won't be runnable by people who don't have an updated image [13:11] I meant adding the qmake binary package to 5.3rtm qtbase packaging [13:12] oh, if it doesn't need qtbase 5.4 it might be ok [13:12] although getting click + qmake-cross to work involved some ugly/unpleasant apt problems when creating chroot [13:13] i'm just very wary of such things, because we recently ran into a problem after 5.4 landed in vivid, with the way clicks were being built in jenkins [13:13] as they were being built on vivid, not rtm [13:14] I'm also wary, it's a rather complex path to fully enable click cross-qmake building in rtm since it wasn't a piece of cake in vivid either when it was done [13:14] and introducing it had a potential to break image building (which it did) etc [13:14] Mirv: the description of bug 1393697 says that that binary is provided with qt 5.3 [13:14] bug 1393697 in click (Ubuntu) "Cross qmake to the chroots" [High,Confirmed] https://launchpad.net/bugs/1393697 [13:16] mardy: in 5.3.2, in vivid, involving many other updated packages like click, ubuntu-touch-meta and even Oxide (which was then reverted later though) because it complicates the click chroot creation afaik [13:16] mardy: so getting qmake-cross package in rtm 5.3.0 qtbase is not the biggest problem, but getting something functional using it is more complex [13:17] anyway, vivid is supposed to be "stable" soon, right? :) [13:17] yes, in a "few weeks". again depending on how quickly all bugs are fixed :) [13:18] it might also take a few weeks before we'd have qmake-cross working inside click chroot for rtm-14.09 [13:19] Mirv: so, you are saying that if I isolate the patch which generates qmake-cross and apply that to 5.3.0, I still won't be able to use it? [13:20] mardy: no, I didn't read the backlog at that point. the commit is there, you can recompile qtbase, but getting the qmake into automatically created click chroots might be more complicated. but I think you might even just get the 5.3.2 qmake-cross and try it out. [13:20] mardy: the packaging change was http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtbase-opensource-src/revision/199 [13:21] plus some fixes in later commits [13:22] mardy: .deb at https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.3.2+dfsg-4ubuntu9/+build/6754505/+files/qt5-qmake-arm-linux-gnueabihf_5.3.2%2Bdfsg-4ubuntu9_amd64.deb [13:22] mardy: if you copy the binary manually to the chroot, it might work (but it might be it would need to be built from 5.3.0) [13:22] you can open the .deb with file-roller and extract the file from /usr/bin/ [13:23] Mirv: excellent, I'll try [13:23] mardy: yeah, sorry, it all depends on whether you need something to hack with or if you want something Zoltan offers to all users :) [13:25] Mirv: first let's see how well it works, then we can think whether it's worth the pain :-) [13:25] dobey, FSVO "soon" [13:26] ogra_: well, hopefully before W is stable ;) [13:27] * ogra_ sstill has his doubts :P [13:27] heh [13:28] ogra_: I'm gonna be cheeky and say patches welcome :P [13:28] ogra_: I will see what I kind do [13:29] nik90, me too then :) [13:29] s/kind/can [13:29] :D [13:30] t1mp: I added the example to the MP. I am hoping that I won't be asked to write a test :P [13:33] dholbach: yo, do you remember this place https://youtu.be/tNPZGc0WmfM?t=18s ? [13:34] daker, which nanosecond shot do you mean? :) [13:34] but yeah - very nice :) [13:36] dholbach: this one https://i.imgur.com/1xUTFIo.png [13:37] yes, thought so :) [13:37] => https://plus.google.com/photos?hl=en%26gpsrc=gplp0&pid=5697853008942523554&oid=109795858099658821877 [13:38] beautiful, yes :) [13:39] now let's wait for the movie :) [13:48] ogra_: Is the shadow sufficient? http://imgur.com/bfR0aPr [13:50] nik90, totally ! [13:51] nik90, i also added a minor hack to make buttons active/inactive in my branch ... (probably wrongly by using opacity 0.5 for the action icon) [13:51] since i want the back/forward actions to be non-active when there is no history in the webview [13:52] ogra_: ah, well I am converting those buttons into actionButtons (currently they are basically a qml rectangle) which would provide haptic feedback and also expose the "enabled" property. [13:52] ogra_: But I guess visually that can be indicated by reducing the opacity of the button [13:52] line 83 and 92 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/Main.qml [13:53] line 11 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/UCSComponents/RadialAction.qml and line 96 in http://bazaar.launchpad.net/~ogra/junk/alternate-webapp-container/view/head:/UCSComponents/RadialBottomEdge.qml [13:54] ogra_: ok I will add that functionality as well in UCS. You would get that automatically when you update the component using ucs [13:54] (oh, and 118 in the last file) [13:54] nik90, heh, well, my approach was rather hackish ... cp /opt/..../dekko/.../UCS /opt/.../blah/ [13:55] i'll roll a proper build script later :) [13:55] ogra_: hehe..whatever works for you [13:55] (this is all after work stuff so it goes a bit slower) [13:57] Hey, I am developing my first Ubuntu (Touch) app, which I hope to run on my Aquaris 4.5E. Now I've seen that the ListItems I plan to use intensively are being overhauled in Ubuntu.Components 1.2. Now my question is, should I target 1.2 or 1.1? My answer will depend on what the Aquaris will run and how fast updates will be pushed to that device. Is there documentation on this matter? === _salem is now known as salem_ [14:00] LangeOortjes, I would urge you towards using the new components. [14:01] balloons, any pointers as to what sites/repositories/lists to follow to keep in the loop on these developments? [14:02] LangeOortjes: the phones (BQ, N4, Meizu) etc will all transition to vivid (which provides the new listitems) soon enough ~2-10 weeks [14:02] that's perfect! [14:02] LangeOortjes: the transition will happen when the QA team give it the green signal *only* everything continues to work as expected [14:02] without any regressions [14:03] that makes sense === salem_ is now known as _salem [14:03] LangeOortjes: so if you want to release your app now then you would need to target 1.1. If not go for 1.2 [14:03] LangeOortjes, to stay in the loop, checkout the phone mailing list: https://lists.launchpad.net/ubuntu-phone/ [14:03] and most importantly have fun LangeOortjes ! [14:04] LangeOortjes: the current core apps (like clock) for instance, have 2 branches one for the current rtm and another for 1.2 (devel) [14:04] LangeOortjes: good luck with your app! [14:04] balloons, fun I am already having. [14:05] nik90, thanks [14:06] nik90: it is always good to write a test ;) [14:08] t1mp: ;-) [14:08] nik90: I approved https://code.launchpad.net/~nik90/ubuntu-ui-toolkit/fix-slider-bubble-width/+merge/253620 [14:08] thnx [14:08] nik90: no happroval yet, we are using our staging to land some final things to vivid, after that we'll land new stuff to staging [14:08] t1mp: sure np. I will try to be on the lookout for these kind of low hanging bugs [14:09] ok :) I'll let you know when I happrove it [14:11] t1mp: If I want to backport to vivid later, I am guessing I would need to propose it against vivid as well? Considering this is just a bug fix.. [14:12] t1mp: also, on vivid desktop do you open the toolkit pro file and build it using qtcreator? At the moment I am doing a hackish way of making code changes in qtc and then building and testing it via the terminal [14:13] t1mp: nik90: this change has no new API to 1.2 so why not to happrove it? [14:13] nik90: open Ubuntu-sdk.pro in QtC [14:13] nik90: then build it [14:14] zsombi: I see that it defaults to debug mode, I suppose that is fine? [14:14] nik90: if you want to run some test app you can add to run [14:14] nik90: yes, you can change it any tiem to release... [14:14] time [14:14] zsombi: ok, [14:15] nik90: if you disable shadow build, and want to run some sample test app from tests/resources, simply use -I modules argument to qmlscene [14:16] nik90: also, you can launch teh test apps using tests/launcher/launcher with -I modules and -touch [14:16] nik90: that can be helpful as you get all mouse events as touch [14:16] ah ok [14:20] zsombi: is ucdeprecatedtheme.cpp new or a copy of an existing file? [14:21] t1mp: it's a copy of UCTheme API, prepared to deisplay deprecation note on MR #4 [14:21] zsombi: I thought we only land approved bug fixes in vivid now? [14:21] t1mp: wasn't this a bugfix? [14:21] t1mp: bugfixes, have you seen any special list that limits us to fix only certain bugs? [14:22] zsombi: yes it is. What I thought is that we have about 4 bugs that we agreed on for vivid and the rest goes to w? [14:22] zsombi: no I haven't seen that list [14:23] zsombi, nik90: ok, this MR looks safe. I'll happrove it. [14:23] t1mp: afaik only new features go to w, bugfixes still go to Vivid... [14:23]