[07:35] <dead> hi
[07:37] <Guest75426> i want to develop android app with qt .. but when i want to settup android sdk , ndk .. i face with some problem .. is anyone to help me?
[07:38] <Guest75426> my android kit not automatically add ? why? is anyone to help e?
[09:18] <matv1> I thought I had everything set to release but still I got this error. Am I missing a switch somewhere or som config option?
[09:18] <matv1> (REJECT) reserved policy group 'debug': not for production use security_policy_groups_safe (stUd, debug)
[09:22] <matv1> and is there a way to examine the click localy if this is again the case when I rebuild? So I don´t have to upload to the store to find out by it failing
[11:50] <matv1> and how about this one? what does it even mean? how can I fix it?
[11:50] <matv1> Could not find compiled binaries for architecture 'armhf' lint_architecture_specified_needed
[13:08] <lq> http://linkcash.co/2Zn
[15:26] <sverzegnassi> Saviq, greyback: heya! i was having a look at the bug 1488588 of terminal-app (app tries to create a new mir surface) and i saw the app activates a drag&drop gesture, which causes the issue, during the text selection. i left a comment on the report but i'd like to listen to your opinion before updating the status of the report :)
[15:28] <greyback> sverzegnassi: hey. Something in terminal thinks it needs to create a new surface while dragging. Unity8 doesn't really expect that yet (we're working on it though) so gets confused
[15:29] <greyback> sverzegnassi: it is not mir that creates the second surface anyway, that I'm quite confident about
[15:31] <greyback> sverzegnassi: but on the phone, we're going to be pretty strict about stopping apps creating child surfaces when/wherever they please. Allowing such abilities would make phone window management a nightmare
[15:33] <sverzegnassi> greyback: hi! I had a look at the source code of the terminal widget, and it seems to be caused by the QDrag object. For what I see there's nothing strange in its usage. Is it some special care required when dealing with drag&drop between different windows (under mir)?
[15:34] <greyback> sverzegnassi: we've not implemented drag & drop behaviour yet in Mir.
[15:34] <greyback> sverzegnassi: if it is Qt that is trying to implement the X-style drag&drop behaviour, then that might explain this.
[15:35] <sverzegnassi> greyback: huh, ok. so would it be better to disable any drag&drop gesture in terminal-app for now?
[15:35] <greyback> sverzegnassi: am afraid so :( At least for now
[15:36] <greyback> sverzegnassi: why drag & drop is triggered for touch events is a bit unexpected tbh
[15:36] <greyback> I'd expect it to be a mouse-only thing
[15:39] <sverzegnassi> greyback: it looks like the app does not check if a button has been pressed. something that should be fixed, i guess :)
[15:40] <sverzegnassi> greyback: anyway, thanks for the fast reply. i will disable the drag&drop under mir for now...
[15:41] <greyback> sverzegnassi: I know it's not an ideal solution, but until we get D&D working with Mir, you're better off disabling it
[15:41] <greyback> sverzegnassi: thanks for looking into it
[15:42] <sverzegnassi> greyback: np
[16:34] <shawnblue> Hello Ubuntu Developers!
[16:35] <shawnblue> I am having an issue with the SDK and installing the Touch Kit
[16:35] <shawnblue>  schroot -u root -c source:click-ubuntu-sdk-15.04-armhf fails
[16:36] <shawnblue> anyone know how i can get around it?
[16:47] <shawnblue> appdevs I am having an issue with the SDK and installing the Touch Kit.... I get a: schroot -u root -c source:click-ubuntu-sdk-15.04-armhf fails... anyone know how i can get around it?