[00:02] <mhall119> ahoneybun: that means you are somewhere doing foo.actualValue where 'foo' is null
[00:44] <ahoneybun> any clues about this: https://plus.google.com/+ChloeJohnson/posts/97M5g2aXrJQ
[01:00] <ahoneybun> mhall119: still here?
[01:32] <mhall119> ahoneybun: only off and on
[01:34] <mhall119> ahoneybun: no idea about that, sorry, he should ask in #ubuntu-touch during work hours
[01:34] <mhall119> or email ubuntu-phone ML
[02:07] <ahoneybun> is there a reason why my buttons are not all visiable in the combobutton
[07:00] <dholbach> good morning
[08:02] <aypac> \msg popey hey
[08:31] <popey> aypac: yo
[10:27] <mivoligo> mzanetti: hi
[10:28] <mzanetti> mivoligo, hi
[10:28] <mivoligo> mzanetti: just added sounds and music to the levelpack, I think it's ready :)
[10:29] <mzanetti> oh really, cool!
[10:29] <mzanetti> will try to get it merged tonight then
[10:29] <mivoligo> great, thanks :)
[10:52] <Masternoob> Can anyone tell me if there is any progress on Bug 1309042?
[10:55] <popey> Masternoob: no.
[10:55] <Masternoob> :(
[10:55] <popey> it won't progress until we move away from our current sync tool
[10:58] <Masternoob> ah ok...is the change in the sync tool somthing that's planed or is it actively in developement?
[11:01] <Masternoob> and is there a bug/wish to track this?
[11:34] <kalikiana> loicm: I tried your orientation fix for ubuntushape, at least for buttons I see no difference https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-dfdt-factors-fix/+merge/259692
[11:36] <loicm> kalikiana: ok thanks, testing should be done on the phone using a MainView with automaticOrientation set to false, rotate the device, then ensure there's an update, current behaviour is anti-aliasing and shadows on the shape are broken, with the branch it's fixed (actually it should)
[11:37] <loicm> kalikiana: or just rotate the phone while using the shell, and scroll -> all the shapes are incorrectly anti-aliased
[11:45] <kalikiana> loicm: http://geraldfield.org/orientationButtons.png
[11:45] <kalikiana> that's rotated on my laptop
[11:46] <kalikiana> and it's with and without your fixes
[11:47] <loicm> kalikiana: that's odd
[11:48] <kalikiana> loicm: it's been like that for a while so when I saw your fix I was assuming that was the motivation for it
[11:49] <loicm> kalikiana: try to lock the gallery, go to the progressbar page and rotate
[11:49] <loicm> kalikiana: this was broken before, and I'm sure this fixes it
[11:49] <loicm> kalikiana: (well at least that particular  case)
[11:50] <loicm> kalikiana: lock the gallery by modifying the MainView directly btw
[11:51] <kalikiana> loicm: what do you mean by locked?
[11:51] <loicm> kalikiana: set automaticOrientation to false
[11:52] <kalikiana> ah
[12:03] <kalikiana> loicm: wow, now I see it
[12:03] <kalikiana> it looks much like what I see on the desktop
[12:03] <kalikiana> now I wonder what's needed to fix it for all cases
[12:04] <loicm> kalikiana: you mean you see the AA issue without the patch?
[12:04] <kalikiana> loicm: yes, sorry for the ambiguity
[12:05] <loicm> kalikiana: disappeared with the patch?
[12:06] <jjw> Someone here？
[12:13] <kalikiana> loicm: looks perfect with your changes
[12:29] <loicm> kalikiana: got disconnected, don't know if you've talked to me
[12:30] <kalikiana> loicm: no worries, I added a comment https://code.launchpad.net/~loic.molinari/ubuntu-ui-toolkit/ubuntu-ui-toolkit-dfdt-factors-fix/+merge/259692 the fix is fine as far as I can tell, and as mentioned my main concern being it's very hard to know if it has any surprising side effects
[12:32] <loicm> kalikiana: I really don't think so, but I could be wrong
[12:32] <kalikiana> loicm: don't think what?
[12:33] <loicm> kalikiana: that there's side effects
[12:33] <loicm> kalikiana: good thing with this patch also, is the AA parameter are changed after the timeout defined in the orientation helper
[12:34] <loicm> kalikiana: since it's watching for the same screen prop changes
[12:34] <kalikiana> loicm: ah, yes. I'm just fundamentally suspicious as we can't unit test it. and we know of two cases where it won't work
[16:15] <mhall119> pmcgowan: do we have plans yet for releasing ubuntu-sdk-15.10-dev1?
[16:18] <pmcgowan> mhall119, its in that bug assigned to mvo, i think we need to decide what to call it as it will also need to live in 15.04 as we discussed
[16:19] <pmcgowan> perhaps the name doesn't matter
[16:19] <nik90> pmcgowan, mhall119: Would that mean that the current 15.04 images will support the 15.10 framework?
[16:19] <mhall119> pmcgowan: right, the framework names aren't stricly dependent on Ubuntu release versions, they've just coincided so far
[16:19] <pmcgowan> nik90, not exactly
[16:19] <pmcgowan> future 5.04 based releases will support new apis
[16:19] <pmcgowan> aka 15.10-dev
[16:20] <pmcgowan> or 15.04.1-dev or something
[16:20] <nik90> ok
[16:20] <pmcgowan> mhall119, maybe we need to have a quick call to firm it up
[16:20] <mhall119> nik90: so the phone images will be based on Ubuntu 15.05 until the switch to snappy (if I understand "the plan" correctly) but they will have additional APIs added
[16:20] <bzoltan> mhall119: pmcgowan: there is not much to release ... the store json file just should be extended with that string
[16:20] <pmcgowan> since its not gettingresolved on its own
[16:21] <mhall119> pmcgowan: works for me, I'm available all afternoon today, and tomorrow afternoon (but not morning)
[16:21] <mhall119> wait, sorry, not Thursday morning
[16:21] <pmcgowan> mhall119, ok let me see when mvo and bzoltan are available and we can decide
[16:21]  * mhall119 is thinking (wishing) it was wednesday already
[16:21] <nik90> mhall119: understood..so future OTAs have the potential to support Ubuntu.Components 1.3 and app devs can use that by switching to the newer framework version
[16:22] <nik90> while sticking to ubuntu 15.04 base
[16:22] <kalikiana> zsombi: wanna review? https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/darkBackgroundText/+merge/260647 the theme fix is checked with design (as you can see in the bug comments)
[16:22] <mhall119> nik90: correct
[16:22] <mhall119> nik90: we just need to give a name to this new framework and use it in 1) the store 2) the SDK 3) the devportal and 4) the device images
[16:23] <mhall119> pmcgowan: maybe we should do as Android and just give a sequential version number
[16:24] <pmcgowan> mhall119, oh man we discussed that originally :)
[16:24] <mhall119> I remember :)
[16:24] <pmcgowan> I got out voted
[16:24] <mhall119> the first api docs were published as sdk-1.0
[16:24] <nik90> mhall119: just do make sure to announce the release of the new framework (when the above 4 areas have been updated) so that app devs can then start to use it.
[16:25] <mhall119> nik90: absolutely, it will be on developer.u.c
[16:26] <nik90> awesome
[16:26] <bzoltan> mhall119: pmcgowan: This file you need to fix https://myapps.developer.ubuntu.com/dev/api/click-framework/
[16:27] <mhall119> bzoltan: ack, we know what needs to be done and where, it's only a matter of deciding on a name and coordinating the work
[19:18] <ahoneybun> mhall119: with 4-6 TextFields, how would you switch between them?
[19:18] <ahoneybun> opps again
[19:19] <mhall119> ahoneybun: you mean like tab-key navigation?
[19:19] <ahoneybun> no
[19:19] <ahoneybun> a button maybe?
[19:20] <mhall119> ahoneybun: I don't understand the setup you're talking about
[19:20] <mhall119> do you have screenshots or code samples?
[19:20] <ahoneybun> I thought touching the textfield would switch the focus
[19:20] <mhall119> it should
[19:20] <ahoneybun> sure let me grab
[19:20] <ahoneybun> I think the setup I have disables that as I set the focus by default
[19:21] <mhall119> ah, that might be the problem, yeah
[19:21] <ahoneybun> http://pastebin.ubuntu.com/11526714/
[19:21] <ahoneybun> but if I pull it out it breaks
[19:21] <ahoneybun> I kinda know why but I would have to find a different way to add
[19:21] <ahoneybun> it is a scorekeeper
[19:21] <ahoneybun> so I need to add numbers and remove them
[19:22] <ahoneybun> incoming ss
[19:22] <ahoneybun> http://imgur.com/M0RpaIC
[19:23] <ahoneybun>     property TextField focused: score1 : this sets the focus to TextField id: score1
[19:23] <ahoneybun> so I need a way to switch the focus from that textfield
[19:25] <mhall119> ahoneybun: where is actualValue coming from?
[19:25] <nik90> ahoneybun: your setup looks awesome..kde plasma 5..which ubuntu version are you running this on?
[19:25] <ahoneybun> property int actualValue: 0
[19:25] <ahoneybun> nik90: Kubuntu 15.04
[19:25] <ahoneybun> thanks also
[19:26] <ahoneybun> ahayzen: helped me with this a lot
[19:26] <mhall119> ahoneybun: oh, I was looking elsewhere, ok
[19:26] <mhall119> ahoneybun: ok, so what happens now when you press a button, does it update score1?
[19:26] <ahoneybun> yes
[19:26] <ahoneybun> only score1
[19:27] <mhall119> right, that's what I would expect
[19:27] <mhall119> ahoneybun: I don't see any code that changes the 'focused' variable
[19:27] <ahoneybun> I've been trying to use combobutton, a listview and a few others to make switching TextFields much better
[19:27] <ahoneybun> mhall119: thats the problem I'm having, I don't know how
[19:27] <ahoneybun> like I said ahayzen did a lot of it
[19:28] <ahoneybun> the math behind it
[19:29] <ahoneybun> I'm thinking of just using a button to switch the focus but then the user has to hit it many times to get to the score they want to edit
[19:29] <ahoneybun> ComboButtons never fit all the Buttons right
[19:29] <mhall119> ahoneybun: try putting an onActiveFocusChanged handler on each of your score# TextFields, and if activeFocus == true, make that field the Column.focused
[19:30]  * ahoneybun thinks
[19:30] <mhall119> If I'm reading https://developer.ubuntu.com/api/apps/qml/sdk-14.10/QtQuick.Item/#activeFocus-prop properly, the activeFocus variable should change when the component gets or loses keyboard focus
[19:32] <ahoneybun> mhall119: I;m a bit lost
[19:33] <ahoneybun> not sure what  handler is tbh
[19:34] <ahoneybun> oh wait reading
[19:34] <mhall119> ahoneybun: just a property change handler
[19:35] <ahoneybun> https://bugreports.qt.io/browse/QTBUG-37954 ?
[19:35] <mhall119> ahoneybun: http://pastebin.ubuntu.com/11526931/ is what I'm suggesting (I haven't tested it yet though)
[19:36] <mhall119> ahoneybun: that shouldn't be relevant to you
[19:36] <ahoneybun> I was looking at the handler example
[19:37] <mivoligo> ahoneybun: instead of using "property TextField focused: score1" you can use "property bool isSelected: false" for each TextField. Then on clicking on given TextField "isSelected" changes value. That way a user could update several scores at once and you don't have to rely on "focused"
[19:38] <ahoneybun> way above me
[19:38] <ahoneybun> that worked mhall119
[19:38] <mhall119> \o/
[19:39] <mhall119> ahoneybun: so in QML, any property of an item will automatically create an on<propertyName>Changed signal that you can react to
[19:40] <ahoneybun> property?
[19:40] <mhall119> since QtQuick.Item has an activeFocus property that is changed when it gets or loses keyboard focus, you can use the corresponding onActiveFocusChanged signal to do something
[19:40] <ahoneybun> I just type things and hope lol
[19:40] <mhall119> ahoneybun: any named variable of a component type
[19:40] <ahoneybun> hasClearButton: false ?
[19:40] <ahoneybun> property
[19:41] <ahoneybun> bool propery
[19:41] <ahoneybun> sorry just saying things out load helps me
[19:43] <mhall119> ahoneybun: https://developer.ubuntu.com/api/apps/qml/sdk-14.10/QtQml.qtqml-syntax-signals/ would be good to read through
[19:43] <ahoneybun> so the user clicks the other TextField and the system knows that this happened = so you can use this cause to haave a effect: that TextField focused changes
[19:43] <mhall119> ahoneybun: yup
[19:44] <ahoneybun> mhall119: be ready for my questions at SELF lol
[19:44] <mhall119> Qt changes the activeFocus property when the user touches the TextField, it then calls any javascript in it's onActiveFocusChanged
[19:44] <mhall119> ahoneybun: I'm going to give a presentation on app development, though I wasn't planning on going into this level of detail
[19:44] <ahoneybun> I meant outside of the class
[19:45] <ahoneybun> lets keep it simple for newbies :)
[19:45] <mhall119> ahoneybun: I'll be more than glad to help :)
[19:45] <ahoneybun> thanks mhall119  as always :)
[19:46] <ahoneybun> and thank you mivoligo for that option too :)
[19:46] <mhall119> ahoneybun: once you understand QML, it will all make so much sense
[19:46] <mivoligo> ahoneybun: :)
[19:46] <ahoneybun> mhall119: this time I'll have my N4 :)
[19:46] <ahoneybun> mhall119: I understand it more then C++
[19:46] <ahoneybun> I need more C++
[19:47] <ahoneybun> mhall119: I'm working on :  https://launchpad.net/gazeteer btw
[19:47] <ahoneybun> a whole new UI thanks to some feedback
[19:48]  * mhall119 also needs to learn more C++
[19:48] <mhall119> ahoneybun: you should try writing a Scope to learn C++
[19:49] <ahoneybun> mhall119: I like scopes. but they are not for me
[19:49] <ahoneybun> way way way above me
[19:49] <ahoneybun> I've tried
[19:50] <mhall119> ahoneybun: I think they've simplified the template recently, might be worth taking another look
[19:50] <mhall119> I know it's on my TODO list :)
[19:56] <ahoneybun> mhall119: from what I saw a while ago they made all the examples to websites . but I know very little of API, REST and they stuff
[19:56] <ahoneybun> explaining those would be very helpful
[19:56] <ahoneybun> and JSON and such
[20:05] <ahoneybun> mhall119: how would I disable the keyboard?
[20:07] <ahoneybun> inputMask : string looks like it
[20:09] <mhall119> ahoneybun: I don't think that's it
[20:10] <mhall119> you mean you don't want the keyboard to pop up?
[20:11] <ahoneybun> well what would be reason for the buttons?
[20:14] <ahoneybun> mhall119: also the SIM problem was with Cricket but I might be what I did
[20:15] <ahoneybun> if I setup the APN for data, and I send a picture it disables the data till I reboot
[20:18] <ahoneybun> I want to use my N4 with Ubuntu as my daily driver but it is hard to go back from my OnePlus One lol
[20:27]  * ahoneybun uploads the changes to his branch
[20:36] <ahoneybun> ahayzen: something is up with my buttons width
[20:37] <ahoneybun> mivoligo: still around?
[20:38] <mivoligo> ahoneybun: yes
[20:38] <ahoneybun> am I doing something wrong here: http://pastebin.ubuntu.com/11528074/ ?
[20:38] <ahoneybun> with the width of the buttons
[20:40] <ahayzen> ahoneybun, you haven't taken the spacing into account i think
[20:40] <mivoligo> ahoneybun: ahayzen was faster :)
[20:41] <ahayzen> heh
[20:41] <ahoneybun> so - units.gu(1) on each button ahayzen?
[20:41] <ahoneybun> thanks mivoligo too
[20:41] <ahayzen> erm
[20:41] <ahayzen> width: (row3.width - units.gu(2)) / 3 ... would work i think
[20:42] <ahoneybun> to each?
[20:42] <ahayzen> yeah
[20:43] <ahoneybun> let me try then
[20:43] <ahayzen> surely you can do like... width: (row3.width - (row3.children.length - 1) * row3.spacing) / row3.children.length .. or something aha
[20:43] <ahayzen> you should really read up about repeaters as well ;-)
[20:43] <ahoneybun> repeaters can't do onClicked no?
[20:44] <ahayzen> yeah they can like the Button would be the delegate of the repeater
[20:44] <ahayzen> and then you would only have to write the button once
[20:44] <ahoneybun> samples you mad man
[20:44] <ahayzen> it would be a big change to the code but you could do the same with your rows as well and it'd probably half the size of the code if you got it working
[20:45] <ahayzen> http://doc.qt.io/qt-5/qml-qtquick-repeater.html
[20:45] <ahoneybun> I'll throw it into my testbed in min
[20:46] <ahoneybun> units.gu(1) looks better
[20:46] <ahayzen> hehe
[20:47] <ahoneybun> looks much better then ahayzen again
[20:47] <ahoneybun> I try out things in my testbed project lol
[20:47] <ahayzen> no problem
[20:48]  * ahoneybun throws it on his N4
[20:48] <ahoneybun> seems sending a pic message breaks my data
[20:49] <ahoneybun> ahayzen: could use this on the uDeck idea
[20:49] <ahoneybun> https://developer.ubuntu.com/api/apps/qml/sdk-15.04/QtQuick.Flipable/
[20:49] <ahoneybun> to flip the card from back to front
[20:50] <ahayzen> uDeck?
[20:50] <ahoneybun> the membership card app
[20:50] <ahayzen> ah
[20:52]  * ahoneybun trys out repeaters
[20:56] <ahoneybun> ahayzen: QQuickWindow: possible QQuickItem::polish() loop :)
[20:57] <ahayzen> omg that brings back memories
[20:57] <ahayzen> what did you do?
[20:58] <ahoneybun> http://pastebin.ubuntu.com/11528514/
[20:58] <ahoneybun> also we can't use spacing?
[20:59] <ahayzen> you should be able to use the spacing
[21:00] <ahoneybun> noe
[21:00] <ahoneybun> nope
[21:00] <ahayzen> try adding the width: parent.width back to the row
[21:01] <ahoneybun> odd
[21:01] <ahoneybun> not spacing works
[21:01] <ahoneybun> *now
[21:02] <mivoligo> ahoneybun: if you have anchors.fill: parent, you don't need other anchors :)
[21:02] <ahoneybun> ?
[21:02] <mivoligo> in your Column
[21:02] <ahayzen> yeah just fill: and margins:
[21:03] <ahoneybun> the top . bottom etc ?
[21:03] <mivoligo> yep
[21:03] <ahoneybun> oh ok
[21:03] <ahoneybun> idk I think I copied from somewhere
[21:07] <ahoneybun> ahayzen: http://pastebin.ubuntu.com/11528610/ : mathPart is not defined
[21:07] <ahoneybun> but it is right there
[21:08] <ahayzen> magic, put an id on the column then do the id.mathPart
[21:08] <ahoneybun> I did not need that in Gazeteer
[21:09] <mivoligo> ahoneybun: it'd work if the mathPart was defined in the MainView
[21:10] <ahoneybun> I changed things
[21:10] <ahoneybun> http://pastebin.ubuntu.com/11528641/
[21:10] <ahoneybun> it is
[21:10] <mivoligo> ahoneybun: it is in Column
[21:10] <ahayzen> yeah just put an id: myColumn on your Column... then do myColumn.mathPart
[21:11] <ahoneybun> I changed parent.parent.focused.actualValue += 2 * mathPart to actualValue += 1 * mathPart
[21:11] <ahoneybun> got it
[21:11] <ahoneybun> label.actualValue += *mathPart
[21:13] <ahoneybun> how would I do +1 +2 +3 with repeaters
[21:13] <ahoneybun> since this is set for them all : onClicked: label.actualValue += 1 * mathPart
[21:14] <mivoligo> instead of "1" use "index+1"
[21:14] <ahoneybun> awesomenesss
[21:15]  * ahayzen senses ahoneybun is learning the awesomeness of repeaters ;-)
[21:16] <mivoligo> :D
[21:17] <ahoneybun> I'm getting to label them would be "text: index+1 ?
[21:17] <ahoneybun> *guessing
[21:17] <mivoligo> ahoneybun: you learn fast :)
[21:17] <ahoneybun> I;m right :)
[21:17] <ahayzen> try it ;-)
[21:17] <ahayzen> \o/
[21:17] <ahoneybun> yay!
[21:19] <ahoneybun> mivoligo: ahayzen http://pastebin.ubuntu.com/11528794/
[21:19] <ahoneybun> working all good
[21:19] <ahoneybun> 1-6 add right
[21:19] <ahayzen> sweat now to the same for the Rows ;-)
[21:20] <ahoneybun> I'll try
[21:20] <ahoneybun> ahayzen:  that would go under the Column is the repeater for buttons went under rows
[21:20] <ahayzen> yup
[21:21] <ahayzen> you may only be able to do it for the last 3 rows?
[21:21] <ahayzen> and not the top one as that is different
[21:21] <ahoneybun> as a example?
[21:21] <ahayzen> oh no the top is the same
[21:21] <ahayzen> so it'll be Column { Repeater { Row { Repeater { Button {
[21:22] <ahayzen> take a copy of what you have now incase it doesn't work out ;-)
[21:22] <ahoneybun> well I'm just working in my testbed atm
[21:22] <ahoneybun> proving it works till I copy it to the main project at hand :)
[21:22] <ahayzen> hehe
[21:23]  * ahoneybun pushes the current work to LP anyway
[21:25] <mivoligo> ahoneybun: instead of rows, you can use Grid
[21:26] <ahoneybun> oh>
[21:26] <mivoligo> for the scores, I mean
[21:27] <ahayzen> ooo yeah good plan
[21:27] <ahoneybun> textfields?
[21:27] <mivoligo> yes
[21:29]  * ahoneybun is still working on Row Repeater
[21:29] <mivoligo> for buttons?
[21:29] <ahoneybun> in total
[21:29] <ahoneybun> yea
[21:30] <ahoneybun> just the number buttons
[21:30] <ahoneybun> I;ll look into Grid in amin
[21:30] <ahoneybun> or so
[21:31] <ahoneybun> ahayzen: now this does kinda work
[21:31] <ahayzen> \o/
[21:31] <ahoneybun> but I have 1 2 3 4 5 6 7 8 9 buttons
[21:31] <ahayzen> what was the target?
[21:32] <ahoneybun> ?
[21:32] <ahoneybun> right now it make 9 buttons thaat all add 1
[21:32] <ahayzen> oh well the value needs to be coming from the index
[21:33] <ahoneybun> no clue on that
[21:33] <mivoligo> screenshot?
[21:33] <ahayzen> paste the code?
[21:33] <ahoneybun> http://pastebin.ubuntu.com/11528903/
[21:34] <ahayzen> hmm what happens with nested repeaters and the index value again?
[21:34] <mivoligo> (index+1)
[21:34] <ahoneybun> all the buttons add 1 2 3
[21:34] <ahoneybun> 123 123 123
[21:35] <ahayzen> yeah they will
[21:35] <ahayzen> you need to * by the index of the outer repeater
[21:35] <ahayzen> like add property int rowIndex: index .. to the outer repeater
[21:36] <ahayzen> then do  + (rowIndex - 1) * 3  or something
[21:36] <ahoneybun> property in rowIndex: index where?
[21:37] <ahoneybun> main row repeater?
[21:37] <ahayzen> inside the Row {
[21:37] <ahayzen> sorry lol
[21:37]  * ahayzen is thinking on the fly
[21:37] <mivoligo> it's easier to go with Grid in this case I htink
[21:37] <ahayzen> yeah it is
[21:38] <ahoneybun> property int rowIndex: index ?
[21:38] <ahoneybun> nothing special
[21:38] <ahoneybun> ?
[21:38] <ahayzen> Grid vs GridView lol
[21:39] <mivoligo> ahoneybun: put index+1 into brackets first
[21:39] <ahoneybun> brackets?
[21:39] <ahoneybun> onClicked: labelScore.actualValue += index+1 * mathPart
[21:39] <ahoneybun> this is what I have currently
[21:40] <mivoligo> so do (index+1)
[21:40] <ahoneybun> k
[21:40] <ahayzen> like = (index + rowIndex) * 3 * mathPart
[21:40] <ahayzen> would maybe work for all the rows?
[21:42] <mivoligo> ahoneybun: but seriously, if you need 9 buttons, it's much easier with Grid
[21:42] <ahoneybun> that add 3
[21:43]  * ahoneybun looks up Grid
[21:44] <ahayzen> hmm = (index + (rowIndex * 3)) * mathPart ...is probably it but yeah go Grid ;-)
[21:46] <mivoligo> ahoneybun: simple example from my app: http://bazaar.launchpad.net/~mpredotka/big-moving-text/trunk/view/head:/qml/ColorPicker.qml
[21:48] <ahoneybun> it makes no rows
[21:49] <mivoligo> do you use "model: 9"?
[21:49] <ahoneybun> no.
[21:49] <mivoligo> :)
[21:50] <ahoneybun> what is the reason for rows: 3 then?
[21:51] <mivoligo> that's the size of grit but you have to specify how many elements go into it
[21:52] <mivoligo> so if you used 3, the rest of the grit is empty
[21:52] <ahoneybun> http://pastebin.ubuntu.com/11529194/
[21:53] <mivoligo> get rid of the mainRow completely
[21:53] <mivoligo> use just Grid
[21:54] <ahoneybun> breaks
[21:54] <mivoligo> and in Grid do: columns:3 ; rows: 3
[21:54] <ahoneybun> done
[21:54] <ahoneybun> nothing on the screen
[21:54] <mivoligo> and model: 9
[21:54] <ahoneybun> nothing
[21:55] <mivoligo> get rid of model: 3 from repeater
[21:56] <ahoneybun> so no repeater?
[21:56] <mivoligo> ahoneybun: sorry, I'm not thinking correctly, on emoment
[21:56] <ahoneybun> all I see atm is the label
[21:56] <ahoneybun> for the score
[22:04] <mivoligo> ahoneybun: try this: http://paste2.org/YI6NDZHa
[22:05] <mivoligo> ahoneybun: you'll probably need to specify Grid width and height or anchors
[22:08] <ahoneybun> yea the width and height worked
[22:08] <ahoneybun> btw what you had was the same that I had
[22:08] <mivoligo> :)
[22:09] <mivoligo> ok, good luck with the code ahoneybun, I'm off to bed :)
[22:10] <ahoneybun> night mivoligo thanks for everything
[22:10] <mivoligo> o/
[22:15] <ahoneybun> the grid works great btw ahayzen
[22:15] <ahayzen> \o/
[22:16] <ahoneybun> cuts a lot of code
[22:16] <ahoneybun> http://pastebin.ubuntu.com/11529560/
[22:17] <ahayzen> heh
[22:17] <ahayzen> :-)
[22:18] <ahoneybun> ahayzen: could you make it when you click on a toolbaritem or button and it changes the model: #
[22:18] <ahoneybun> ?
[22:18] <ahayzen> yeah i guess
[22:18] <ahoneybun> if a person wanted more then 4 players?
[22:18] <ahayzen> you would need to adjust the columns # as well
[22:19] <ahoneybun> I'm not talking about the Grid
[22:19] <ahayzen> oh
[22:20] <ahoneybun> about this now: return Math.round(Math.random()) [22:20] <ahoneybun> is there a way to change from 2 variables to 4?
[22:20] <ahoneybun> randomly select a player
[22:21] <ahayzen> yeah you could do that
[22:22] <ahoneybun> I;ve tried " 0 ? "Player 1" : "Player 2" : "Player 3" like that
[22:22] <ahayzen> no...
[22:22] <ahayzen> there are quite a few ways of doing it
[22:24] <ahoneybun> oh ok
[22:25] <ahayzen> like you could just pick a number between 1 and 4 i guess
[22:25] <ahoneybun> how would that look in code though?
[22:29] <ahayzen> just like lookup generating random numbers between ranges http://stackoverflow.com/questions/1527803/generating-random-numbers-in-javascript-in-a-specific-range
[22:30] <ahoneybun> dear god
[22:32]  * ahoneybun closes up for the day
[22:32] <ahayzen> haha sounds like a plan
[22:33] <ahoneybun> I've learned a lot thanks ahayzen
[22:33] <ahoneybun> and miv as well
[22:33] <ahayzen> no problem
[22:33] <ahoneybun> I know he is gone
[22:35] <ahoneybun> ahayzen: do you use your Ubuntu phone as your daily driver?
[22:35] <ahayzen> yup
[22:35] <ahoneybun> with the OnePlus One I just cannot
[22:36] <ahoneybun> also I need working GPS lol
[22:36] <ahayzen> damn, i thought you had a N4?
[22:36] <ahoneybun> I do
[22:37] <ahayzen> ...that has working GPS?...
[22:37] <ahoneybun> no app has amazing GPS features
[22:37] <ahoneybun> nothing beats Google Maps
[22:38] <ahayzen> https://uappexplorer.com/app/navigator.costales ?
[22:38] <ahoneybun> that crap
[22:38] <ahoneybun> always says "Waiting for GPS"
[22:39] <ahayzen> ah damn :-/
[22:39] <ahoneybun> I need that for Akademy
[22:39] <ahayzen> when the location-service works it like locks instantly for me :-)
[22:39] <ahoneybun> nice
[22:40] <ahoneybun> I mean it might because the bad signal in my room
[22:41] <ahoneybun> wait it got me
[22:47] <ahoneybun> I'll try it as a daily driver sometime
[22:48] <ahoneybun> ahayzen: the BQ device?
[23:47] <ahoneybun> Elleo: I really love PodBird
[23:50] <Elleo> ahoneybun: cool :) glad to hear it, nik90's been responsible for a lot of the recent work on it though :)
[23:51] <ahoneybun> really nice stuff Elleo and nik90 :)
[23:51] <ahoneybun> I was listening to some Ubuntu podcast on the way to work in the car
[23:51] <ahoneybun> popey's of course
[23:51] <ahoneybun> lol
[23:51] <Elleo> heh