[06:54] <didrocks> zsombi: hey, I think I may doing something wrong with a Flickable + OptionSelector. Would appreciate if you can give a hand. Here is a small example: http://paste.ubuntu.com/12005153/
[06:54] <didrocks> what happens is:
[06:54] <didrocks> - the flickable is not with contentY: 0 at start, it only behaves that way once drag
[06:55] <didrocks> - it doesn't seem to take into account the new OptionSelector height when I click on it (seems it's clipped, and so, I don't have the options)
[06:55] <didrocks> - this behavior is """fixed""" when I add the foo label. However, I find the OptionSelector animation to expand its choice to be jumpy
[06:56] <didrocks> I hope the example is skimmed down enough to find what wrong in my practice :)
[06:57] <dholbach> good morning
[06:57] <didrocks> hey dholbach
[06:57] <dholbach> hey didrocks
[06:59] <zsombi> didrocks: the contentY is not at 0 at start as MainView header management adjusts it to be header.height
[07:01] <didrocks> zsombi: doesn't seem to be recalculated in that example until I drag it
[07:01] <zsombi> didrocks: let me check
[07:07] <zsombi> didrocks: btw, you know that Column's width in the Flickable is 0
[07:08] <didrocks> zsombi: yeah, I changed it locally
[07:08] <zsombi> didrocks: because Column's parent is the Flickable.contentItem, not the flickable :)
[07:10] <zsombi> didrocks: ah, yeah, the flickable's topMargin and contentY is screwed.... t1mp may help you on that, he may know a trick to get this fixed
[07:11] <zsombi> didrocks: but, also beware that childrentRect doesn't get updated :/
[07:11] <didrocks> zsombi: yeah, that's my second point, right?
[07:11] <zsombi> didrocks: yes
[07:11] <didrocks> zsombi: so, how to deal with this properly?
[07:13] <zsombi> didrocks: actually I managed to fix the top margin :)
[07:14] <zsombi> didrocks: but the OptionSelector ain't seem to work properly...
[07:14] <zsombi> didrocks: if I put a label after it, it expands nicely
[07:15] <zsombi> didrocks: if it is teh last component, you can see the background not expanding at all
[07:15] <zsombi> didrocks: so OptionSelector looks the same, doesn't expand
[07:16] <didrocks> zsombi: you don't need to put a label after it, it can be before (that's why I put a label and comment it)
[07:16] <zsombi> didrocks: ahha...
[07:16] <didrocks> zsombi: but anything less hackish? :)
[07:16] <zsombi> didrocks: that seems to be a bug of OptionSelector then...
[07:17] <didrocks> t1mp should be bugged as well on this?
[07:17] <zsombi> didrocks: nope...
[07:18] <zsombi> didrocks: OptionSelector is a bloatware... since we got it as a present, we got more problems with it than beneffit :(
[07:18] <zsombi> didrocks: but, the flickable issue:
[07:18] <didrocks> zsombi: as long as you provide me an alternative, I'm fine :)
[07:19] <zsombi> didrocks: give an ID to your flickable (i.e. id: flickable), and set the width of the column using that (width: flickable.width)
[07:19] <zsombi> didrocks: then, Flickable.contentHeight: column.height
[07:19] <zsombi> didrocks: this will solve you the top margin issue
[07:20] <zsombi> didrocks: also the childrentRect changes
[07:20] <didrocks> zsombi: hum, I get the top margin issue fixed, but not the childrentRect one?
[07:21] <zsombi> didrocks: for the OptionSelector, I'd use a Label with an empty string to get it working, and put it after the OptionSelector... I don't know whether we will have time to fix this bug on the component which is on teh deprecation list :(
 didrocks: but, the flickable issue:
[07:21] <zsombi> didrocks: you had two issues, I provided a fix for that first :)
[07:21] <didrocks> "zsombi | didrocks: also the childrentRect changes" -> I thought you mentionned this non refresh
[07:22] <didrocks> zsombi: what component should be used then, if no OptionSelector?
[07:22] <didrocks> (also, there is no deprecation mention as of now)
[07:22] <zsombi> didrocks: yes, it doesn't refresh, but that won't necessarily work with the extra label either... at least not always updates properly
[07:22] <didrocks> it doesn't with the extra label
[07:22] <didrocks> with empty text
[07:22] <zsombi> didrocks: OptionSelector is on teh deprecation list, we are working on a component set to replace it, but we need time
[07:23] <zsombi> didrocks: it works for me....
[07:23] <zsombi> didrocks: empty text means you have at least a space... sorry
[07:23] <didrocks> ah
[07:23] <zsombi> my mistake :)
[07:23] <didrocks> yeah, the animation is horribly sloppy, but at least it works :)
[07:24] <didrocks> ok, at least, I can log bugs and refer to that :)
[07:24] <didrocks> thanks zsombi
[07:24] <zsombi> it is, but that is just one problem with the OptionSelector
[07:24] <zsombi> didrocks: there are bunch of others, like just not good for any app :/
[07:24] <didrocks> zsombi: well, we have to use something until you come with the new set I guess :)
[07:24] <zsombi> didrocks: I know ;(
[07:25] <zsombi> didrocks: also design changed a lot, and changing anything on the component is a pain :(
[07:25] <didrocks> at least, the bugs will document for devs what's the workaround
[07:25] <didrocks> zsombi: welcome to ubuntu! (on design changing a lot ;))
[07:25] <zsombi> didrocks: and we ahve ItemSelector and OptionSelector, both crap
[07:25] <zsombi> *have
[07:30] <justCarakas> sudo su
[07:30] <justCarakas> oops :)
[08:21] <rarara> hey, I need help with my javascript animation in the qml canvas. None of the methods which are supposed to redraw, like requestPaint() or clearRect(0,0,width, height) redraw my canvas, but if i resize the window, i see progress.
[08:21] <rarara> it really drives me NUTS!
[08:22] <rarara> code is here: http://pastebin.ubuntu.com/12005466/
[08:33] <rarara> it would be great to know which method is called even when the canvas resizes. Becausse if i resize it manually or from within the application, it redraws nicely.
[11:04] <kivi> I receieved some spam on google plus from a company who's logo made me thing it was some ubuntu product https://updraftplus.com/shop/updraftplus-premium/?
[13:43] <balloons> popey, is file manager going to get an update anytime soon?
[13:44] <balloons> I'd like to unpublish my x86 build of it :-)
[13:48] <popey> balloons: yeah, will set aside some time to update it on friday if I can
[15:25] <NymeriaFr> hello guys
[15:25] <NymeriaFr> I need your help, I cannot export my application into my Aquaris E4.5
[15:25] <NymeriaFr> Sdk-Launcher> Received a failed event
[15:26] <NymeriaFr> do you know why I have this error ?
[19:03] <mhall119> kalikiana: would be great to have a blog post about the new components on developer.u.c
[19:04] <kalikiana> mhall119: I guess I can do one. g+ is just tons easier :-D
[19:06] <mhall119> kalikiana: it is, but blogs last longer and are easier to find
[22:06] <Paddy_NI> Hello I am trying to reset the Ubuntu SDK to it's "factory defaults" if that is the correct term, would anyone know where I should look?
[22:06] <Paddy_NI> The options don't immediately seem to offer any such option
[22:07] <Paddy_NI> I guess I could "apt-get purge" but that seems a little too much like the nuclear option
[23:05] <skinux> Can Ubuntu apps (which live in the top panel area) be written in Java?
[23:22] <JanC> skinux: do you mean indicators?
[23:22] <skinux> To begin with I suppose that would be it.
[23:40] <JanC> skinux: it should be possible, but I don't know about any ready-to-use Java library