=== chihchun_afk is now known as chihchun === athairus is now known as afkthairus === masse is now known as MasseR === JamesTait is now known as Guest1123 === Guest1123 is now known as JamesTait === JMulholland_ is now known as JMulholland [10:20] t1mp, ping [10:22] nik90: hi [10:24] t1mp, Hi, I am having an issue in my app with the latest UITK in rc-proposed where the back button disappeared in a few pages. I was able to narrow it down the reason to https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1565811 [10:24] Launchpad bug 1565811 in ubuntu-ui-toolkit (Ubuntu) "PageHeader should not have a back action if it's the first page on the stack" [High,Fix committed] [10:25] t1mp, I have a setup similar to http://paste.ubuntu.com/15920303/ [10:25] where I have a so called "Home Page" which I don't push into the pagestack. [10:25] Instead I push the child pages only to the stack. As a result, when I push them, the depth is 1 [10:26] why do you do that? [10:26] in any case, you can set PageHeader.leadingActionBar.actions = [ Action { iconName: "back"; onTriggered: pageStack.pop(); text: "Back" } ] [10:27] t1mp, I do that because sometimes I want to pop all child pages to return to the home page using the clear() function. [10:27] If I had pushed the Home Page, then that would be popped from the stack as well. [10:27] UITK Pagestack pop() function doesnt allow me to dictate how many pages I want to pop like the upstream Qt Stackview [10:28] t1mp, And yes, at the moment I have resorted to using a custom back button. [10:28] But that feels hacky :P [10:29] we can only have one default behavior for the back action, either we show it or we don't show it when there is one page on the stack [10:29] we had it documented as not showing for one page, and it worked like that with the old header, so I think the bug you pasted above was valid, and it should not show the back action [10:30] Hmm [10:30] I don't know the whole structure of your app, but I would say that the home page can be the first page on the stack [10:30] fair enough [10:30] as a side note, maybe you want to switch to the AdaptivePageLayout :) [10:31] t1mp, it is for uNav (default navigation app on the phone) [10:31] because it will support convergence [10:31] so the breakage is a bit concerning and we don't yet have an idea about how we want to converge. [10:31] we're still brainstorming about the design [10:31] ok [10:32] so you relied on our bug when it was not obvious that it was a bug. [10:32] t1mp, one more question, will the SDK add default keyboard shortcuts to the back button like "Escape" ? [10:33] if I unfix the bug to fix the app, that will break other apps again [10:33] t1mp, yes I wasn't aware it was a bug [10:33] right [10:33] nik90: not that I know of, but we can ask a designer [10:33] Femma: ^ will we have default keyboard shortcuts for a back action in a page? [10:34] t1mp, I will give it further thought to see if I can also push the HomePage (map view) to the stack. [10:34] but as of the moment, I know that sometimes we need to jump from stack depth 2 to the map view. [10:34] nik90: there is keyboard navigation however so you can use TAB to select the back button and then trigger it with (I think) enter or space [10:34] and I don't see how to do that without using the clear() function [10:35] nik90: or multiple pop()s [10:35] nik90: I don't know the designs for unav. Perhaps the map could be a separate layer not in the stack [10:35] perhaps that's what you have now :) [10:35] t1mp, that's what we have now :P [10:35] whcih is why our child pages have depth 1 [10:36] t1mp: nik90 at the moment, the way to achieve that would be via focus. There are currently no plans to implement a back keyboard shortcut, however if there is a requirement/use case for it then we can definitely think about including it [10:37] t1mp, see this is why you don't automate stuff in the SDK side :P .. if app devs want to hide the back button, just give them a method to do so. [10:38] nik90: yeah. Now they can by setting leadingActionBar.actions = [] [10:38] t1mp, yup [10:40] nik90: maybe that is a good reason to switch to the APL :) [10:41] nik90: it can do everything that the PageStack can do, but it has a more flexible removePage(page) function [10:41] nik90: apl.removePages(mapPage) would do the trick for you [10:42] nik90: https://developer.ubuntu.com/api/apps/qml/sdk-15.04.4/Ubuntu.Components.AdaptivePageLayout/#removePages-method [10:46] t1mp, ooh that's nice..I will try to migrate to it [10:46] thnx [10:47] nik90: cool. Let me know if there are any issues [10:47] or if you discover more advantages of the APL over PageStack so we can convince more people to migrate :) [10:51] :) [11:22] mzanetti: hello :) [11:22] o/ [11:22] mzanetti: I thought it may be useful for you and nik90 to know what you both are doing for navigation, to avoid duplication of the effort [11:23] nik90: what's up with unav? Are you planning a big redesign/rewrite? [11:26] yeah, I've been talking to Marcos and Nekhelesh already. As I said, I didn't really want to compete with uNav but rather just play a bit with the QML location api [11:26] and well, turns out its working very nicely === _salem is now known as salem_ === davidcalle_ is now known as davidcalle [13:06] bzoltan_: zsombi: Kaleo: UOS is coming up ,and I'd like to have a session showing off our UITK and specifically the convergence/adaptive features of our components, which one of you can lead that session? === boiko_ is now known as boiko [14:38] Hi there. I got an error: opening shm. I read that it is a platform error. what can I do? [14:38] it crashes HaloWord and I think some more other apps. [14:40] my platform was ubuntu 15.04 OTA-10.1, on a bq Aquaris E5. [15:06] mhall119: it will be zsombi === charles_ is now known as charles [15:23] hey. does any one know this: failed to open shm error? [15:42] thanks bzoltan_ === salem_ is now known as _salem === afkthairus is now known as athairus === _salem is now known as salem_ === chesedo- is now known as chesedo === pat_ is now known as pmcgowan === chihchun is now known as chihchun_afk === salem_ is now known as _salem