[Touch-packages] [Bug 1502091] Re: inconsistent and unpredictable scrolling behaviour

[Zsombor Egri]

Unfortunately there's not much we can do about this on the toolkit
level. This must be handled on the ListView or Flickable level, and
those are not toolkit elements. We have UbuntuListView derived from
ListView which could do something about the scrolling speed. But that
requires the app to use the component instead of using the QtQuick's
ListView. However the problem with the ListViews is that those are
usually scrolling slowly, especially when the delegate uses the old
Ubuntu.Components.ListItem components. Switching to UITK 1.3
ListItem/SlotsLayout/ListItemLayout would speed up the scrolling,
however if the model used to fill the view is slow, you will still
notice some lags in scrolling.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1502091

Title:
  inconsistent and unpredictable scrolling behaviour

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  inconsistent and unpredictable scrolling behaviour

  i am unable to predict the scrolling pace, it's or too fast and i have
  to tap on the screen to stop the scrolling or is too slow.  also
  scrolling in telegram app is very diff than scrolling in g+ app or HN
  app. try scrolling fast in HN app (it's impossible)
  https://uappexplorer.com/app/com.ubuntu.developer.rayalez.hackernews

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502091/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1502091] Re: inconsistent and unpredictable scrolling behaviour

[Zsombor Egri]

Right, I think that was discussed even before on this bug
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1348557

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1502091

Title:
  inconsistent and unpredictable scrolling behaviour

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  inconsistent and unpredictable scrolling behaviour

  i am unable to predict the scrolling pace, it's or too fast and i have
  to tap on the screen to stop the scrolling or is too slow.  also
  scrolling in telegram app is very diff than scrolling in g+ app or HN
  app. try scrolling fast in HN app (it's impossible)
  https://uappexplorer.com/app/com.ubuntu.developer.rayalez.hackernews

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1502091/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1507910] Re: UITK: error: 'emit' was not declared in this scope

[Zsombor Egri]

Simple fix: 
#define emit Q_EMIT
#include .
#undef emit

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1507910

Title:
  UITK: error: 'emit' was not declared in this scope

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  New with Qt 5.5.1:

  --
  In file included from plugin/ucubuntushape.cpp:37:0:
  
/usr/include/x86_64-linux-gnu/qt5/QtQuick/5.5.1/QtQuick/privateqquickimage_p.h: 
In member function 'virtual void QQuickImage::emitAutoTransformBaseChanged()':
  
/usr/include/x86_64-linux-gnu/qt5/QtQuick/5.5.1/QtQuick/private/qquickimage_p.h:91:67:
 error: 'emit' was not declared in this scope
   virtual void emitAutoTransformBaseChanged() Q_DECL_OVERRIDE { emit 
autoTransformChanged(); }
     ^
  --

  https://launchpadlibrarian.net/221749985/buildlog_ubuntu-wily-amd64
  .ubuntu-ui-
  
toolkit_1.3.1676%2B15.10.20151008-0ubuntu2~wily1~qt551~1%2Bhack2_BUILDING.txt.gz

  More information about Qt 5.5 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1507910/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508114] Re: AbstractButton doesn't have a minimum size for the touch area

[Zsombor Egri]

This can be achieved only if the AbstractButton is not having clip set,
as otherwise the clipping will restrict the sensing area too.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1508114

Title:
  AbstractButton doesn't have a minimum size for the touch area

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  AbstractButton should have a minimum touch area of 4x4GU, as reported
  in the UI Toolkit spec (currently only in the ListItem layouts
  section, it has to be moved to a generic section)

  That means

  AbstractButton {
  width: units.gu(6)
  height: units.gu(6)
  }

  has a touch region of 6x6GUs, while

  AbstractButton {
 width: units.gu(2)
 height: units.gu(2)
  }

  must have a touch region of 4x4GU.

  UI Toolkit spec:
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1508114/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1392306] Re: [sdk] Swipe to remove/answer/switch inconsistent

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1392306

Title:
  [sdk] Swipe to remove/answer/switch inconsistent

Status in Ubuntu UX:
  Won't Fix
Status in dialer-app package in Ubuntu:
  Confirmed
Status in ubuntu-settings-components package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Won't Fix

Bug description:
  Hi guys, I noticed the horizontal swipes in the interface behave in
  different ways meaning different things, I wish we could have common
  positive/negative meanings on the directions they are applied.

  On snap decision calls, a left to right swipe has a positive meaning, answer 
the call.
  On indicator message, a left to right swipe has a negative meaning, remove 
the message.

  I guess the same applies to apps, contact app does left to right with
  a negative meaning, to remove the contact.

  Lock screen can be swiped away any direction, but on the edge demo we
  recommend doing a right to left for "removing" the lockscreen.

  A right to left edge swipe has a meaning of switching context, like
  swiping it away (maybe negative meaning or we should ignore the case?)

  Can we come up with a consistent behaviour? What you think?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1392306/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492343] Re: Pages hidden in an AdpativePageLayout stack have their width changed to zero

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1492343

Title:
  Pages hidden in an AdpativePageLayout stack have their width changed
  to zero

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  As shown in this example [0], if you select the "Albums for artist"
  button to push a page onto the stack, you can see in the console that
  the width of the old component is changed to zero, which causes it
  then to reflow as the width is increased when it is brought back into
  view. Instead, the width should not be changed when the page is
  hidden.

  0 - http://pastebin.ubuntu.com/12274053/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1492343/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Zsombor Egri]

@Joey Ubuntu.Content is not part of the Ubuntu UI Toolkit project the
version of that is not driven by the toolkit versioning.

The toolkit has the following modules:
Ubuntu.Components 1.3
Ubuntu.Components.ListItems 1.3
Ubuntu.Components.Pickers 1.3
Ubuntu.Components.Popups 1.3
Ubuntu.Components.Styles 1.3
Ubuntu.Components.Themes 1.3
Ubuntu.Components.Themes.Ambiance 1.3
Ubuntu.Components.Themes.SuruDark 1.3

The following modules were not altered recently:
Ubuntu.Layouts 1.0
Ubuntu.PerformanceMetrics 1.0

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1508363

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
  Ubuntu.Components 1.3
  Ubuntu.Components.ListItems 1.3
  Ubuntu.Components.Pickers 1.3
  Ubuntu.Components.Popups 1.3
  Ubuntu.Components.Styles 1.3
  Ubuntu.Components.Themes 1.3
  Ubuntu.Components.Themes.Ambiance 1.3
  Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
  Ubuntu.Layouts 1.0
  Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  QUESTION:
  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Zsombor Egri]

** Description changed:

  The migration to 1.3 needs to happen in a coordinated way, so that shell
  and all apps we care of migrate within the same OTA window to reduce
  visual inconsistencies to a minimum.
  
  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.
  
  NOTES:
  - The toolkit has the following modules:
  Ubuntu.Components 1.3
  Ubuntu.Components.ListItems 1.3
  Ubuntu.Components.Pickers 1.3
  Ubuntu.Components.Popups 1.3
  Ubuntu.Components.Styles 1.3
  Ubuntu.Components.Themes 1.3
  Ubuntu.Components.Themes.Ambiance 1.3
  Ubuntu.Components.Themes.SuruDark 1.3
  
  - The following modules were not altered recently:
  Ubuntu.Layouts 1.0
  Ubuntu.PerformanceMetrics 1.0
  
  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property
  
  QUESTION:
- In manifest.json file, should we use:
-    "framework": "ubuntu-sdk-15.04-qml",
- or
-    "framework": "ubuntu-sdk-15.04.1-qml",
- ?
+ In manifest.json file use:
+    "framework": "ubuntu-sdk-15.04.1-qml"

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1508363

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  New
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  In Progress
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
  Ubuntu.Components 1.3
  Ubuntu.Components.ListItems 1.3
  Ubuntu.Components.Pickers 1.3
  Ubuntu.Components.Popups 1.3
  Ubuntu.Components.Styles 1.3
  Ubuntu.Components.Themes 1.3
  Ubuntu.Components.Themes.Ambiance 1.3
  Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
  Ubuntu.Layouts 1.0
  Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  QUESTION:
  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500409] Re: Dragging within a ListItem does not work

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1500409

Title:
  Dragging within a ListItem does not work

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  If we try to drag an item that is parented to a ListItem, the drag is 
interrupted after a few pixels, or sometimes it is not even started.
  In the example attached, try to drag any of the red rectangles, and it will 
fail as explained above. Dragging the ListItem itself is also not working, in 
the same way.
  This used to work before  a recent release, and is causing bug #1499437

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1500409/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500416] Re: Swiping should not be possible when leadingActions or trailingActions is an empty list

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1500416

Title:
  Swiping should not be possible when leadingActions or trailingActions
  is an empty list

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Whenever the leadingActions or trailingActions property is assigned an
  empty list, it should not allow swiping in the corresponding
  direction. Right now it does, as shown in the attached example.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1500416/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Zsombor Egri]

Victor and others, in order to get the header height you need to set the
Page.header first. Page.header is null by default, so no wonder you
cannot get the height. You can do something like

Page {
header: PageHeader {
}

}

Then you will have the header set and you can use that to get the
height. The component is present in UITK trunk, however I do not see its
documentation under d.u.c...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1508363

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508363] Re: Coordinated migration to UITK 1.3

[Zsombor Egri]

Victor,

You are right, there is one header per application. Which means that all
pages in an application use that header. However that would be broken
when you'd use the AdaptivePageLayout, which has as many headers as
columns. Therefore we are preparing to move the header in the page, so
each page will get a header of its own. Yet we have both solutions in
place, thats' why you still see a header even if you don't set one on
the Page.

So, in the future of 1.3, you will have to set the header of the page
yourself. Which means there will be as many headers as many pages
require one. The one from MainView will disappear once we finish all the
work we have for the header and its subcomponents.

When you say "With the updated imports to UITK 1.3 we are unable to do
things like the following: edgeLoader.item.flickable.contentY =
-page.header.height" - I am sorry to say that the Page.header property
was never documented, and used for private purposes. We do not promise
any compatibility for private or undocumented properties, especially
when the property comes from a super type, which is also internal.
Whilst it is a regression, switching to 1.3 would anyways require you to
go with the way I described before - specifying the header for your page
within the page.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1508363

Title:
  Coordinated migration to UITK 1.3

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  In Progress
Status in Ubuntu Notes app:
  New
Status in Ubuntu Calculator App:
  In Progress
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  In Progress
Status in Ubuntu Document Viewer App:
  In Progress
Status in Ubuntu Shorts App:
  In Progress
Status in Ubuntu Weather App:
  Triaged
Status in Weather:
  New
Status in address-book-app package in Ubuntu:
  In Progress
Status in calendar-app package in Ubuntu:
  Confirmed
Status in camera-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  In Progress
Status in gallery-app package in Ubuntu:
  In Progress
Status in messaging-app package in Ubuntu:
  In Progress
Status in music-app package in Ubuntu:
  Confirmed
Status in reminders-app package in Ubuntu:
  Fix Committed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Fix Released
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  In Progress
Status in ubuntu-weather-app package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress
Status in webbrowser-app package in Ubuntu:
  Fix Released

Bug description:
  The migration to 1.3 needs to happen in a coordinated way, so that
  shell and all apps we care of migrate within the same OTA window to
  reduce visual inconsistencies to a minimum.

  This bug is a means to collect all the projects affected and keep tabs
  on what's happening.

  NOTES:
  - The toolkit has the following modules:
 Ubuntu.Components 1.3
 Ubuntu.Components.ListItems 1.3
 Ubuntu.Components.Pickers 1.3
 Ubuntu.Components.Popups 1.3
 Ubuntu.Components.Styles 1.3
 Ubuntu.Components.Themes 1.3
 Ubuntu.Components.Themes.Ambiance 1.3
 Ubuntu.Components.Themes.SuruDark 1.3

  - The following modules were not altered recently:
 Ubuntu.Layouts 1.0
 Ubuntu.PerformanceMetrics 1.0

  - Theme is now theme (lowercase)
  - PageHeadStyle now has a "config" property

  In manifest.json file use:
     "framework": "ubuntu-sdk-15.04.1-qml"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1508363/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510201] Re: AdaptativeLayout take longer to show a page

[Zsombor Egri]

I'll take a look on it but I'm pretty sure any optimisation on
AdaptivePageLayout will not make it to OTA8.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510201

Title:
  AdaptativeLayout take longer to show a page

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Device: krillin
  Image: Ubuntu 15.04 (r153)

  
  I created a small/simple example with Pages using the new AdaptativeLayout.

  On this example the second page takes about 2.6 secs to show the page.
  While it only took 1.3 secs (Still a long time) when using PageStack.

  
  OBS:  You can easily change the example to use PageStack just changing the 
commented lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

2015-10-28 13:40:25,358 - WARNING - QQmlExpression: Expression 
file:///usr/share/ubuntu/settings/system/qml-plugins/about/DevMode.qml:94:30 
depends on non-NOTIFYable properties:
2015-10-28 13:40:25,358 - WARNING - StorageAbout::developerMode
2015-10-28 13:40:33,696 - WARNING - QQmlExpression: Expression 
file:///usr/share/ubuntu/settings/system/qml-plugins/about/DevMode.qml:94:30 
depends on non-NOTIFYable properties:
2015-10-28 13:40:33,697 - WARNING - StorageAbout::developerMode

These warnings I assume come to the line [1]. If the property value is
false during the Switch.checked property initialization, the actual
value will not be updated to the Switch, as the property it is bound to
has no notify signal.

[1] http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-
settings/trunk/view/head:/plugins/about/DevMode.qml#L94

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510919

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510919/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510919

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510919/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510919

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510919/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510201] Re: AdaptativeLayout take longer to show a page

[Zsombor Egri]

Alternatively we can add an extra parameter to force page addition to be
synchronous.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510201

Title:
  AdaptativeLayout take longer to show a page

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Device: krillin
  Image: Ubuntu 15.04 (r153)

  
  I created a small/simple example with Pages using the new AdaptativeLayout.

  On this example the second page takes about 2.6 secs to show the page.
  While it only took 1.3 secs (Still a long time) when using PageStack.

  
  OBS:  You can easily change the example to use PageStack just changing the 
commented lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510201] Re: AdaptativeLayout take longer to show a page

[Zsombor Egri]

We profiled this with Florian, and it ends up that Repeater is no longer
creating the bunch of components and then renders, but it creates each
delegate asynchronously after which it renders each of them separately.
So instead of a 1000 block create then render we have 1000 create +
render, and sniffed rendering between creates slows down the things.
This will always happen when page is loaded asynchronously and the
loaded page has a Repeater, until upstream does something with the
Repeater to load faster.

Using ListView with a cache to fit the whole model content behaves
differently, at least the visible items are created in a block
synchronously then rendered, and the rest of the invisible ones are
created asynchronously afterwards. So this may be a better approach for
use cases we have in the attached example.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510201

Title:
  AdaptativeLayout take longer to show a page

Status in Canonical System Image:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Device: krillin
  Image: Ubuntu 15.04 (r153)

  
  I created a small/simple example with Pages using the new AdaptativeLayout.

  On this example the second page takes about 2.6 secs to show the page.
  While it only took 1.3 secs (Still a long time) when using PageStack.

  
  OBS:  You can easily change the example to use PageStack just changing the 
commented lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1511839] Re: On dynamically created pages, head.sections.selectedIndex can't be set to -1

[Zsombor Egri]

Raised to critical as blocks migration to 1.3.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: High => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1511839

Title:
  On dynamically created pages, head.sections.selectedIndex can't be set
  to -1

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Ubuntu.Components version: 1.3

  Some times it is desirable that none of the entries in the 
head.sections.model is selected by default.
  While that works fine on statically created pages, if I define a page inside 
a component, or load it directly from a QML file, this is not respected.

  The following sample QML application reproduces the problem:

  import QtQuick 2.3
  import Ubuntu.Components 1.3

  MainView {
  width: units.gu(30)
  height: units.gu(60)
  Component {
  id: pageComponent
  Page {
  id: page
  title: i18n.tr("The Page")
  head.sections.model: ["one","two","three"]
  head.sections.selectedIndex: -1
  }
  }

  PageStack {
  id: stack
  }

  Component.onCompleted: {
  stack.push(pageComponent)
  }
  }

  Expected result: a page with no section selected.
  What happens: the first section of the header is selected by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511839/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1511839] Re: On dynamically created pages, head.sections.selectedIndex can't be set to -1

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1511839

Title:
  On dynamically created pages, head.sections.selectedIndex can't be set
  to -1

Status in Canonical System Image:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Ubuntu.Components version: 1.3

  Some times it is desirable that none of the entries in the 
head.sections.model is selected by default.
  While that works fine on statically created pages, if I define a page inside 
a component, or load it directly from a QML file, this is not respected.

  The following sample QML application reproduces the problem:

  import QtQuick 2.3
  import Ubuntu.Components 1.3

  MainView {
  width: units.gu(30)
  height: units.gu(60)
  Component {
  id: pageComponent
  Page {
  id: page
  title: i18n.tr("The Page")
  head.sections.model: ["one","two","three"]
  head.sections.selectedIndex: -1
  }
  }

  PageStack {
  id: stack
  }

  Component.onCompleted: {
  stack.push(pageComponent)
  }
  }

  Expected result: a page with no section selected.
  What happens: the first section of the header is selected by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1511839/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510919] Re: developer mode toggle does nothing

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510919

Title:
  developer mode toggle does nothing

Status in Canonical System Image:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Last know good image: 157
  Commit log for 158: 
http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-proposed/158.commitlog

  TEST CASE:
  1. Flash a device with bootstrap or upgrade to latest image
  2. Go to system-settings / About / Developer mode
  3. Toggle developer mode

  ACTUAL RESULT
  On a freshly flashed device, toggling dev mode on does nothing
  On an upgraded device with dev mode enabled, toggling dev mode off does 
nothing

  WORKAROUND
  Flash with --developer-mode

  = original description =
  Using a krillin on rc-proposed, developer mode does not enable an adb shell:

  ubuntu-touch/rc-proposed/bq-aquaris.en #159

  $ ubuntu-device-flash touch --bootstrap --channel ubuntu-touch/rc-
  proposed/bq-aquaris.en --recovery-image recovery-krillin.img

  Then boot device to wizard, walk through (I configured wifi, 
  passcode and have 2 SIMs online in the device). Defaults for location.

  Open System settings | about this phone | developer mode

  Enable developer mode

  On your pc:

  $ adb shell
  error: device not found

  Expected: a phablet shell on the device.

  Additionally, if you now reboot, the setting for developer mode is
  forgotten.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510919/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField/AbstractButton regression/behavior change in 1.3

[Zsombor Egri]

Perhaps the TextField got changed, it should keep the content of the
overlay Items unfocusable by touch...

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField/AbstractButton regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1510201] Re: AdaptativeLayout take longer to show a page

[Zsombor Egri]

I mark this as invalid as it is not the AdaptivePageLayout which makes
the page to load slower but the content of the page, in particular the
QtQuick Repeater component which slows the page loading.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: canonical-devices-system-image
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1510201

Title:
  AdaptativeLayout take longer to show a page

Status in Canonical System Image:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Device: krillin
  Image: Ubuntu 15.04 (r153)

  
  I created a small/simple example with Pages using the new AdaptativeLayout.

  On this example the second page takes about 2.6 secs to show the page.
  While it only took 1.3 secs (Still a long time) when using PageStack.

  
  OBS:  You can easily change the example to use PageStack just changing the 
commented lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1510201/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField/AbstractButton regression/behavior change in 1.3

[Zsombor Egri]

As workaround, set the activeFocusOnPress for the AbstractButton to
false. TextField should set them all automatically.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField/AbstractButton regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField/AbstractButton regression/behavior change in 1.3

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField/AbstractButton regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField/AbstractButton regression/behavior change in 1.3

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField/AbstractButton regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField/AbstractButton regression/behavior change in 1.3

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField/AbstractButton regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField regression/behavior change in 1.3

[Zsombor Egri]

The same happens if you replace the AbstractButton with MouseArea: the
text field suffers focus change.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513897] Re: TextField regression/behavior change in 1.3

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513897

Title:
  TextField regression/behavior change in 1.3

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Having an AbstractButton as secondaryItem of a TextField used to not
  change the TextField focus status when pressing the button but with
  1.3 it does.

  Code at http://paste.ubuntu.com/13125887/

  Is this an intended change or a behaviour regression?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513897/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514173] Re: [listitemlayout] setting RichText format with html image tag leads to crash (segfault)

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514173

Title:
  [listitemlayout] setting RichText format with html image tag leads to
  crash (segfault)

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListItemLayout defines a default main slot, which is currently the
  internal class UCThreeLabelsSlot.

  ListItemLayout currently doesn't set the QML context of the
  UCThsreeLabelsSlot, and UCThreeLabelsSlot doesn't set the QML context
  of its internal UCLabels.

  This leads to a segfault when Qt tries to access the QML context of
  any of the predefined labels in ListItemLayout.

  The following test case triggers the crash:
  ListItemLayout {
  id: layoutTestQmlContext
  title.text: "TEST  "
  title.textFormat: Text.RichText
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514173/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513933] Re: Page.head.sections.selectedIndex does not reset when changing model

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513933

Title:
  Page.head.sections.selectedIndex does not reset when changing model

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Changing Page.head.sections.model does not change the
  Page.head.sections.selectedIndex  even when the model has different
  size.

  I have a page that I need to update the ' Page.head.sections.model '
  dynamically and after change the model or make it empty the
  Page.head.sections.selectedIndex still point to last value used.

  I expect that to reset back to 0 if the model changes.

  Check attached example .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513933/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1195353] Re: SDK should provide support to rearrange items in a ListView

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: ubuntu-ui-toolkit (Ubuntu Vivid)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1195353

Title:
  SDK should provide support to rearrange items in a ListView

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit source package in Vivid:
  Fix Released

Bug description:
  For the clock core app, as per design, it is required to implement
  ListView where the user can drag and drop to rearrange the items in
  the ListView. You can see the official wireframe designs at
  http://design.canonical.com/wp-content/uploads/clock_add_city-
  1024x8901.png to see what I meant.

  It would be best if the SDK can provide support to implement this
  since it may also be useful to other apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1195353/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1289433] Re: "No accounts" doesn't use the list placeholder font style

[Zsombor Egri]

This can be achieved with simple Label within an Item, no need for
special toolkit component.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-system-settings-
online-accounts in Ubuntu.
https://bugs.launchpad.net/bugs/1289433

Title:
  "No accounts" doesn't use the list placeholder font style

Status in Online Accounts setup for Ubuntu Touch:
  Confirmed
Status in ubuntu-system-settings-online-accounts package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Ubuntu Trusty r188

  1. Flash the phone or remove any existing online accounts.
  2. Go to System Settings > "Accounts".

  What you see: "No accounts" in the normal label font style.

  What you should see: "No accounts" in the standard list placeholder
  font style, large and semi-transparent.

  : "If you have none,
  the list of accounts should have 'No accounts' placeholder text..."

  Exactly the same style should be used for "Software is up to date" in
  the Updates screen. If that style is not implemented in the toolkit,
  that should be done first.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-system-settings-online-accounts/+bug/1289433/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1259876] Re: No support for colourizing ListItems.Standard Icon.

[Zsombor Egri]

No changes will be done for ListItems submodule, the new ListItemLayout
gives the freedom to include anything in the slots and thus you can
colorise in whichever way you like.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1259876

Title:
  No support for colourizing ListItems.Standard Icon.

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  Previously we could override the icon and supply our own icon which
  could be coloured. This has now been deprecated for
  iconSource/iconName.

  Use case: 
  The date indicator appointments use colour coding for the calendar. The 
alarm/calendar icon should be keyed in with the specified calendar colour. Want 
to be able to use ListItems.Standard for the event list item.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1259876/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1226329] Re: [TextField] The placeholderText does not apper when inputMask is setted

[Zsombor Egri]

Christian, not sure whether is this still valid.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zsombor Egri (zsombi) => Christian Dywan (kalikiana)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1226329

Title:
  [TextField] The placeholderText does not apper when inputMask  is
  setted

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The inputMask makes the placehorlderText invisible even when the text
  property is empty.

  Example:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: "09/09/"
  }

  
  WORKAROUND:
  TextInputDetail {
  height: units.gu(4)

  // this will never appears
  placeholderText: i18n.tr("Date of birth")
  inputMask: activeFocus ? "09/09/" : ""
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1226329/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514841] Re: [Ubuntu phone] Text in text entry is cut at the bottom (TextArea with autoSize=true)

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514841

Title:
  [Ubuntu  phone] Text in text entry is cut at the bottom (TextArea with
  autoSize=true)

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  When I get a text message and try to answer from the notification text
  entry, the text I write is cut at the bottom. Also the scrollbar is
  visible. Please see attached screenshot. The text reads: „Hej zgadza
  się”.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1514841/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513642] Re: [sdk] Change "Back button" to simple right-swipe from the center of the screen.

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513642

Title:
  [sdk] Change "Back button" to simple right-swipe from the center of
  the screen.

Status in Ubuntu UX:
  Invalid
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Back button is located in left-upper corner.
  Stretching the thumb to that corner is not easy (regardless left- or 
right-hand usage).
  More natural will be using horisontal swipe from the middle of the screen, 
the same way as it's done for shuffling scopes back.
  I think it will work almost everywhere, making interface experience more 
streamlined.

   UX comment ---

  While swiping left and right in the center of the screen for navigational 
purposes works for scopes, it would lead to issues in many other places.
  As stated below, list items have the ability being swiped to the left and to 
the right, which would interfere with the navigation. An other example is the 
camera app, where user access their camera roll/last picture shot.

  This is why the proposed interaction is not suitable navigating
  between applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1513642/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513449] Re: 1.3 DraggingArea reference error MathUtils is not defined

[Zsombor Egri]

This should pop up only if you use Panel in your app. Do you happen to
have that?

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513449

Title:
  1.3 DraggingArea reference error MathUtils is not defined

Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  This shows up in the log:
  - when resizing the app window on desktop (15.04 with phone overlay installed)
  - occasionally on the phone

  I think the error is pretty obvious, so probably the bug report need
  to be super detailed.

  file:///usr/lib/x86_64-linux-
  gnu/qt5/qml/Ubuntu/Components/1.3/DraggingArea.qml:27: ReferenceError:
  MathUtils is not defined

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1513449/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1512180] Re: [datetime] Standard alarms are not work correctly for Timers, after timezone/DST change

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-datetime in
Ubuntu.
https://bugs.launchpad.net/bugs/1512180

Title:
  [datetime] Standard alarms are not work correctly for Timers, after
  timezone/DST change

Status in Canonical System Image:
  Incomplete
Status in Timer:
  Confirmed
Status in Ubuntu Clock App:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  Standard alarms will not work correctly after changing timezone and
  during DST change.

  Steps to reproduce:
  1. Install Timer from Store: https://uappexplorer.com/app/timer.mivoligo
  2. Set timer to 5 minutes
  3. Open Clock app. Look for alarm, and notice that alarm is correctly set
  3. Switch to System Settings -> Time & Date -> Time zone:
  4.  Change Time zone to something different (eg. New York). (Or wait for DST 
change: https://en.wikipedia.org/wiki/Daylight_saving_time)

  Expected behaviour:
  - timer ringing as expected after timezone/DST change

  Current behaviour:
  - alarm is not ringing. (you could check active alarms in "Ubuntu Clock app)

  Proposal solution:
  - introduce new type of alarms, which is based on UTC 
(https://en.wikipedia.org/wiki/Coordinated_Universal_Time) and independent from 
time zones.
  - This alatms will not be visible in applications which is using standard 
alarms (Ubuntu Clock, Ubuntu Calendar etc.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1512180/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1501397] Re: Can't use Action id's in ActionList

[Zsombor Egri]

First, when you declare a list, you can only initialise it with objects,
not with their IDs. Seems we have this limitation on that. See Object
component implementation how its data is implemented.

Second, Page.head.actions is a list, not an object. You are trying to
assign an object to a list.

Better start with reading the docs carefully.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1501397

Title:
  Can't use Action id's in ActionList

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Latest rc-proposed, UbuntuComponents 1.3

  I can't use Action id's to compile an ActionList in order to re-use
  those actions elsewhere.

  Please see example: http://paste.ubuntu.com/12625111/

  You may want to reference ActionSelectionPopover documentation here:
  
https://developer.ubuntu.com/api/devel/ubuntu-12.04/qml/ui-toolkit/qml-ubuntu-components-popups0-actionselectionpopover.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1501397/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1499872] Re: Right swipe showing running apps, some apps are grayed out

[Zsombor Egri]

This is not a toolkit bug, rather Unity8.

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1499872

Title:
  Right swipe showing running apps, some apps are grayed out

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  I am using the Meizu MX4 with the latest updates(15.04 r4). Sometimes
  when I look at my running apps with a right swipe, some of the running
  apps are greyed out (transparent). If I then select the app it opens
  after a few seconds. On checking the running apps again I can now see
  the running app as normal. Please see picture attached.

  Thanks for your hard work,

  Regards

  Dave H

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1499872/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1499845] Re: Expose whether an app has a visible BottomEdge

[Zsombor Egri]

It is way easier to detect on an app whether it is the first run or not
than on shell. Shell would need to keep track about each app on how many
times it has been launched, and that is just not its task.

I mentioned Tutorial component simply because I do see this whole logic being 
tracked by it:
- is this the first launch
- show the required information over a given point with a given animation full 
screen

I definitely see this should be all on the app's hand and not on the
system. Apps know whether they have bottom edge and they should handle
the tutorial. No reason to do extra communication and slow the UI
interaction with that even more than we have to. Toolkit can provide the
building blocks to get this handled without extra burden for the apps.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Opinion

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1499845

Title:
  Expose whether an app has a visible BottomEdge

Status in ubuntu-ui-toolkit package in Ubuntu:
  Opinion

Bug description:
  == The Design ==

  The edge tutorial that is shown during the first-boot is getting a
  redesign [1].

  As part of it, the bottom edge tutorial screen is intended to only
  appear after a certain amount of time and only if a user is opening or
  switching to an app with a bottom edge to drag up.

  When that happens, a page appears covering the whole screen, pointing
  to the bottom and saying "Swipe from the bottom edge to manage the
  app".  Then when the user does swipe up, it fades out as the bottom is
  swiped.   I've attached a screenshot of an early mockup for this (back
  when it was designed for the App scope, not an actual app).

  Since it must cover the entire screen (and turn off the launcher and
  panel during it), it should probably be rendered by the shell (which
  is rendering the rest of the tutorial anyway).  So we have to
  coordinate between the app and the shell.

  There are two main technical difficulties in implementing this, the
  way I see it.  Detecting if the current page has a valid BottomEdge
  and synchronizing the fade-out with the bottom-edge drag.

  [1] https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s

  == Detecting BottomEdge ==

  We need:
  1) A BottomEdge SDK component
  2) That is enabled
  3) That is attached to the bottom edge of the app
  4) That is currently being rendered (might be in a Page that isn't on top 
right now)
  5) That isn't obscured by some other widget or MouseArea

  #5 is going to be hard to detect in the wild west of apps from the
  store.  But one thing we could do restrict this to known-well-behaved
  apps that are shipped by default anyway.  The user is most likely to
  be in one of those early on in their phone experience anyway.

  Once the SDK can detect this situation, it needs to signal it somehow.
  Maybe the "valid-bottom-edge" state can bubble up to qtmir's
  ApplicationManager and then the shell.  Any ideas on the best way to
  do that?

  == Synchronizing fade transition ==

  I'm thinking there are two ways:

  1) Communicate from the app to the shell how far the bottom edge has
  been dragged, as it is being dragged.  Presumably via the same channel
  as we communicate that there is a valid bottom edge in the first
  place.

  2) Fake it and have the shell track the drag itself.  It then needs to
  mirror the input to the app so that it also receives the drag.

  #2 is probably easier.  Slightly brittle in case for whatever reason
  the app interferes with the drag or does something on its own that
  would desynchronize the animation.  But again, if we limit this to
  well-known apps, we can avoid that.

  == Open tasks ==

  1) Get general feedback on these ideas
  2) Determine how feasible it is for the SDK to detect a valid BottomEdge
  3) Determine the best way to signal that state from the SDK up to the shell
  4) Implement it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1499845/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1477363] Re: onDestruction is never called in the QML component

[Zsombor Egri]

In your example, the Page is declared as an instance. When you close the
application, the elements will be destroyed silently, without having
their attached Component.onDestruction called.

When you use a Page declared in the way you reported in a PageStack or
AdaptivePageLayout, the Page will not be destroyed by these components
as it has not been created by the PageStack/AdaptivePagelayout. So you
won't get the onDestruction triggered either. In order to have that
coming, you need to declare your page as component and add that to the
PageStack/AdaptivePageLayout, or in a separate QML document and use
that.


** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1477363

Title:
  onDestruction is never called in the QML component

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  I have created a very simple application, and I want to capture the
  onDestruction event. However, it is never called on a phone, but it is
  called on the desktop. On the page,
  http://developer.ubuntu.com/api/apps/qml/sdk-15.04/Qt.labs.settings.Settings/,
  it is used to save the state of the application.

Page {
  title: i18n.tr("ondestruction")

  Column {
  spacing: units.gu(1)
  anchors {
  margins: units.gu(2)
  fill: parent
  }

  Label {
  id: label
  objectName: "label"

  text: i18n.tr("Hello..")
  }

  Button {
  objectName: "button"
  width: parent.width

  text: i18n.tr("Tap me!")

  onClicked: {
  label.text = i18n.tr("..world!")
  }
  }
  }

  Component.onDestruction: {
  console.log("ondestruction")
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1477363/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1492769] Re: OSK should be closed before removing page from PageStack

[Zsombor Egri]

OSK is removed by the Qt's TextInput or TextEdit components losing
focus. Those lose focus also when the component is deleted or made
invisible. As OSK and the UI are running in separate threads, it is
obvious that you will receive the signal after the page has been closed.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1492769

Title:
  OSK should be closed before removing page from PageStack

Status in ubuntu-keyboard package in Ubuntu:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Hello, I think I have found a bug from PageStack component, see

  https://bugs.launchpad.net/my-webapp-group/+bug/1490493

  I have produced a small app where the bug can be easily reproduced

  https://code.launchpad.net/~matti-rintanikkola-d/+junk/radial-buttom-
  edge-bug

  Reproduce fault: 
  1) Open "Page2" page from Root page by clicking radial action icon "Home"
  2) click website title/url field in order to open keyboard view
  3) without closing the keyboard turn back to the main view
  4) the main view will be opened without radial actions edge button

  Analysis: The visibility of the main view radial edge button is
  toggled by using the connection

  Connections {
  target: Qt.inputMethod
  onVisibleChanged: nav.visible = !nav.visible
  }

  If you do not close the keyboard when turning back to the Root page
  from "Page2" page the main view became visible before the signal
  onVisibleChanged is fired and when it will be fired the radial edge
  button becomes invisible.

  Solution?: Before removing the page from pageStack it should be
  ensured that the keyboard is not visible. Maybe this could be achieved
  simply by adding a function call Qt.inputMethod.hide() before removing
  the page from pageStack.

  Regards,

  Matti

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1492769/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1276808] Re: new API that allows to know what the current mode is (desktop, phone, tablet)

[Zsombor Egri]

As long as it will be back ported to Qt 5.4 I'm OK with it. Otherwise we
need an API of our own till we migrate to Qt 5.6.

** Tags added: convergence

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1276808

Title:
  new API that allows to know what the current mode is (desktop, phone,
  tablet)

Status in Ubuntu HTML5 UI SDK:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  https://docs.google.com/a/canonical.com/document/d
  /1TvvPAxJbxqvCvWhwkdkt15G-BY-neyYfmxXlg9FInUo/edit?disco=AKLL3f4#

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-html5-theme/+bug/1276808/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514850] Re: There is no visual feedback for Header actions with focus

[Zsombor Egri]

No component but text inputs have visual feedback on focus. This is an
ongoing work by design and would be handled through the same change set.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514850

Title:
  There is no visual feedback for Header actions  with focus

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  While implementing  keyboard navigation on address-book I notice that
  the actions in the header (and buttons) are receiving focus but there
  is no visible feedback which action contains the focus.

  Besides that the focus never returns to the page items, as you can see
  on the attached example. Pressing "tab" does not move the focus to
  next item in the chain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514850] Re: There is no visual feedback for Header actions with focus

[Zsombor Egri]

** Tags added: convergence

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514850

Title:
  There is no visual feedback for Header actions  with focus

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  While implementing  keyboard navigation on address-book I notice that
  the actions in the header (and buttons) are receiving focus but there
  is no visible feedback which action contains the focus.

  Besides that the focus never returns to the page items, as you can see
  on the attached example. Pressing "tab" does not move the focus to
  next item in the chain.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514850/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1508114] Re: AbstractButton doesn't have a minimum size for the touch area

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1508114

Title:
  AbstractButton doesn't have a minimum size for the touch area

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  AbstractButton should have a minimum touch area of 4x4GU, as reported
  in the UI Toolkit spec (currently only in the ListItem layouts
  section, it has to be moved to a generic section)

  That means

  AbstractButton {
  width: units.gu(6)
  height: units.gu(6)
  }

  has a touch region of 6x6GUs, while

  AbstractButton {
 width: units.gu(2)
 height: units.gu(2)
  }

  must have a touch region of 4x4GU.

  UI Toolkit spec:
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1508114/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1241506] Re: Confirm Swipe to delete icon color is Gray in Suru themes

[Zsombor Egri]

Ehm, sorry, ListItem's leadingActions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1241506

Title:
  Confirm Swipe to delete icon color is Gray in Suru themes

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  The new confirm-swipe-to-delete trash icon appears gray even while
  using the Suru themes. As a result is stands out from other icons used
  which are generally white. Either provide an option to change the
  color manually or while using Suru themes, it should appear white.

  Attached album showing original (current custom implementation in clock app) 
and the new implementation (as in SDK). The font and icon sizes are also 
different. But this can be tackled in another bug report if necessary.
  http://imgur.com/a/1Xsho

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1241506/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1241506] Re: Confirm Swipe to delete icon color is Gray in Suru themes

[Zsombor Egri]

Deprecated in favour of ListItemLayout.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1241506

Title:
  Confirm Swipe to delete icon color is Gray in Suru themes

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  The new confirm-swipe-to-delete trash icon appears gray even while
  using the Suru themes. As a result is stands out from other icons used
  which are generally white. Either provide an option to change the
  color manually or while using Suru themes, it should appear white.

  Attached album showing original (current custom implementation in clock app) 
and the new implementation (as in SDK). The font and icon sizes are also 
different. But this can be tackled in another bug report if necessary.
  http://imgur.com/a/1Xsho

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1241506/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1340132] Re: Text labels under icons are offset to the right #123 mako

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1340132

Title:
  Text labels under icons are offset to the right #123 mako

Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  The text under icons are offset to the right a bit since #123.

  See screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1340132/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1450846] Re: [SDK] Changing the font / font size...

[Zsombor Egri]

This is not the system theming or so, this is all about the
Accessibility support. We need system wide support for that. Yet we
don't.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1450846

Title:
  [SDK] Changing the font / font size...

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  It would be usefull if the font and the font size could be changed
  espacially for elderly users and  for people with visual problems. So
  content could be read easily.

  Changing colors, features like home screen simplification, large
  icons... would be great, too.

  Should be found in system settings → background

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450846/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1421293] Re: Icon width is inconsistent when height is specified

[Zsombor Egri]

Ahm, Albert, I have worst news for you: design said we have to set the
implicit width/height to 2grid units... so you will have to do more
calculations if we apply that :(

Perhaps we expose the image size so you can decide whether you want to
bind to that or not.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1421293

Title:
  Icon width is inconsistent when height is specified

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The width of an Icon {} depends if the Icon is an SVG coming from
  image://theme/ or a JPG.

  For the SVG the width grows as the units.gu grow, but for the JPEG it
  does not and one has to manually add code to maitain the aspect ratio.

  See the attached code and files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421293/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1355046] Re: Colourized icon with invalid source is black

[Zsombor Egri]

I think this has been fixed indirectly in 1.3 by one OTAx bug where we
had the same issue with the header navigation actions getting black
boxes. I cannot reproduce the bug anymore.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1355046

Title:
  Colourized icon with invalid source is black

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Given the code:

  import QtQuick 2.2
  import Ubuntu.Components 1.1

  Item {
  width: 50
  height: 50

  Icon {
  id: icon
  width: 20
  height: 20
  source: "invalid"
  color: "red"

  anchors.centerIn: parent
  }
  }

  The Icon is black, because the shader has no source to operate on. It
  should probably cough up completely transparent pixels instead?

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.1.1181+14.10.20140806-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7
  Uname: Linux 3.16.0-6-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.14.5-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Aug 11 09:47:22 2014
  SourcePackage: ubuntu-ui-toolkit
  SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 
'system-image-cli'
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1355046/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1515593] Re: head.foregroundColor does not affect icons in the header

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1515593

Title:
  head.foregroundColor does not affect icons in the header

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  According to the documentation of PageHeadConfiguration ( 
https://developer.ubuntu.com/api/apps/qml/sdk-15.04.1/Ubuntu.Components.PageHeadConfiguration
 ) property "foregroundColor" should change the color of the text and icons. 
  Unfortunately it only affects the page title and not icons. Screenshot 
attached.
  Sample code:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  Page {
  id: root_about

  title: "Test page"

  head.foregroundColor: "red"
  head.actions: [
  Action {
  iconName: "camcorder"
  },
  Action {
  iconName: "info"
  }
  ]
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1515593/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1277195] Re: Need to support theme customization via click package

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Opinion

** No longer affects: ubuntu-ui-toolkit

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1277195

Title:
  Need to support theme customization via click package

Status in ubuntu-ui-toolkit package in Ubuntu:
  Opinion

Bug description:
  It would be nice for creative content developers to be able to
  distribute alternate themes via the Click store.  However, the current
  SDK theme uses QML files to theme components, and those files are able
  to read potentially sensitive information from an app and transmit
  them over the internet.  Since the theme code is run in-process with
  the app, there's no way to separately confine it.

  What we could provide, however, is the ability to define just the
  color scheme used (and possibly other purely visual info, such as
  icons), in a file that could be read by the theme's QML, but that
  would not contain any executable code itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1277195/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1246141] Re: ListItem.Standard spacing between icon & label shouldn't be linked to contentsMargin

[Zsombor Egri]

We are deprecating the ListItems sub-module. Please use ListItemLayout
or SlotsLayout instead.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1246141

Title:
  ListItem.Standard spacing between icon & label shouldn't be linked to
  contentsMargin

Status in ubuntu-ui-toolkit package in Ubuntu:
  Won't Fix

Bug description:
  If you set a large contents margin in ListItem.Standard, it shouldn't make a 
large space between icon & label.
  Should stick to units.gu(2)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1246141/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1393485] Re: [SDK] Need a standard way to make an Icon look disabled

[Zsombor Egri]

Same goes for the Labels too. So in general, we need to set different
colors for components when they are disabled.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1393485

Title:
  [SDK] Need a standard way to make an Icon look disabled

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  [Updated description]

  Right now if one wants to use an Icon inside a ListItem.Empty or any other 
AbstractButton derived class, and disable the item, there is no standard way to 
make the Icon look disabled without directly affecting its opacity and/or 
colorization.
  Haviing a standard way to do this would help promoting consistency in the UI.

  --- UX Solution ---
  Agreed. Disabled icons should have 30% opacity by default, but that can be 
changed by the App developer

  –––

  Desired solution:

  Adjust the opacity to 30% (0.3) for all disabled icons. This will be
  consistent with our disabled states on buttons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1393485/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1260793] Re: Error logs from Icon ShaderEffect

[Zsombor Egri]

This was fixed indirectly by an OTA5 (or OTA6?) bug where the header
navigation icons were turned into black boxes, and we got the same error
message when non-visible source was set.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1260793

Title:
  Error logs from Icon ShaderEffect

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Getting the following error log when Icon using a colour shader is
  being set to non-visible

  ShaderEffect: Property 'source' is not assigned a valid texture
  provider (QQuickImage*).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1260793/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1504315] Re: right hand click doubles down on prompts (which autoappear from selected text)

[Zsombor Egri]

The right click has been there for quite some time, before we started
the race for convergence.

There is no "official" way to detect whether we have mouse attached, the
QInpiutDeviceInfo is about to come. Unity8 has ported something from the
upstream code, but we are waiting till upstream ports that back to Qt
5.4. I won't happen, we will have to move some code to the UITK and
provide temporary API for that.

Text input context menu positioning has been improved, I'd suggest you
to check it once more and revisit the bug. Thanks!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1504315

Title:
  right hand click doubles down on prompts (which autoappear from
  selected text)

Status in canonical-pocket-desktop:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  testing windowed mode with mouse
  selected text with left hand mouse button, which brought up tool tip to "copy"
  selected copy, navigated to an empty text box, selected with left hand mouse 
button, tried right hand button click on mouse
  expected tool tip for "paste"
  result was nothing - no combo for raising "paste" including long touch 
actually in this mode.Keyboard ctl+v worked fine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1504315/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514856] Re: Receiving "Ambiguous shortcut" even when action is not in use

[Zsombor Egri]

The contextual actions is in work in progress. Right now, every action
is active, no matter if the component it is attached to is visible or
not. This means you will have several shortcuts set, as page
stacks/adaptive page layouts do not disable them while in background.
The shortcut system therefore cannot decide which shortcut is active...

I am not sure we can fix this for OTA9.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514856

Title:
  Receiving "Ambiguous shortcut" even when action is not in use

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  I am trying to use "Esc" shortcut for several actions on my project
  (most of than for the back button action on Page header), but even
  when only one back button is visible/active/in use I still receiving
  the message "QML Action: Ambiguous shortcut: Esc".

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514856/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514860] Re: OptionSelector does not work with keyboard

[Zsombor Egri]

True, no focus handling is performed on any component, and this belongs
to the focus handling, as the expansion, navigation requires the
component to be focused.

Beside, this component requires heavy redesign.

** Tags added: convergence

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514860

Title:
  OptionSelector does not work with keyboard

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  OptionSelector does not fully work with only keyboard. There is no way
  to select a option on OptionSelector using only the keyboard.

  Pressing the arrows does not navigate on the options. And it does not
  have any visual feedback that it contains focus.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514860/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514822] Re: activeFocusOnTab is not accessible

[Zsombor Egri]

This is there due to the upstream bug logged in
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-
src/+bug/1389721.

But please port your application to use Ubuntu.Components ListItem and
ListItemLayout components, ListItems module will be deprecated in 1.3
and removed in 1.4.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514822

Title:
  activeFocusOnTab is not accessible

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  I am using  QtQuick 2.4 and Ubuntu.Components.ListItems 1.3.

  By default all ListItems receive focus. For my app I want to disable
  focus for some of the items.

  I am trying to set "activeFocusOnTab" to false but I am receiving this error 
message: 
  "ListItem.Empty.activeFocusOnTab" is not available due to component 
versioning"

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514822/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1504551] Re: Text input popover and selection cursors not oriented properly in shell

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1504551

Title:
  Text input popover and selection cursors not oriented properly in
  shell

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  See attached screenshot, tapping twice on the password entry shows the
  text overlay, but it's in hardware orientation, not the real one.

  It's been fixed for dialogs, but we must've missed popovers somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.3.1627+15.10.20150908-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-14.16-generic 4.2.2
  Uname: Linux 4.2.0-14-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct  9 15:17:56 2015
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1504551/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1386579] Re: [SDK] Toolkit lacks radio buttons

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => Confirmed

** No longer affects: ubuntu-ui-toolkit

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1386579

Title:
  [SDK] Toolkit lacks radio buttons

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Currently the toolkit has no radio buttons.

  As a result, developers are using checkboxes for groups of options where only 
one can be selected at a time.
  

  This is misleading. Everywhere else, checking a checkbox toggles its
  state, whereas here special code is used to ensure it remains checked.
  And on every other platform, checking a checkbox doesn't uncheck
  another checkbox.

  : "Radio buttons are one of the three types of
  radio control (along with the radio list and the radio menu), letting
  you choose exactly one from a group of options..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1386579/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1367412] Re: [address book] no landscape support

[Zsombor Egri]

Invalid for toolkit as the application orientation is not a toolkit
restriction.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1367412

Title:
  [address book] no landscape support

Status in Ubuntu UX:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid

Bug description:
  Long contact name handling seems to behave somewhat erratically but
  normally ends in "...". The expectation is that turning the screen
  sideways would allow the full contact name to be shown but the app
  doesn't seem to support this yet.

  -- UX comment--

  The desired solution is that the address book app will be able to rotate into 
landscape. There is a new header design for landscape on mobile and it will be 
part of the UI toolkit. Once the header lands, then the address book can use 
it. 
  As for the long name issue: Once the AB rotates into landscape, long names 
should have more space to be displayed. 

  The new header design for mobile landscape can be found here:
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.a8gwztgmbhpq

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1367412/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1401920] Re: Image extension fails to notify of source changes

[Zsombor Egri]

I checked the issue with .svg and .jpg images, they both seem to work.
sourceChanged() signal is emitted and the source is changed accordingly.

I have tested with QtQuick 2.4 and UITK 1.3.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1401920

Title:
  Image extension fails to notify of source changes

Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete

Bug description:
  When importing Ubuntu.Components, the base Image QML type is enhanced
  (with the UCQQuickImageExtension class) to add transparent support for
  scaling assets.

  This breaks the emission of the sourceChanged signal. Application
  developers cannot implement the onSourceChanged slot to be notified of
  changes to the value of the 'source' property, and this isn’t
  documented anywhere.

  Another issue I’m observing with this custom extension is that an
  image is not reloaded if I do the following, and invoke the reload()
  function on the image (this works if I comment out the import of
  Ubuntu.Components):

  Image {
  cache: false
  function reload() {
  var s = source
  source = ""
  source = s
  }
  }

  Similarly (and maybe even more worrying), actually changing the value
  of the source property (by appending a fragment to the URL) doesn’t
  trigger a reload either, as demonstrated by the attached example
  (requires a random image named "test.jpg" in the same folder).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1401920/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1413121] Re: MainView is missing an API to dynamically set supported orientations

[Zsombor Egri]

We need Mir support for this, and an API we can drive this.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1413121

Title:
  MainView is missing an API to dynamically set supported orientations

Status in QtMir:
  Confirmed
Status in qtubuntu:
  New
Status in qtmir package in Ubuntu:
  Confirmed
Status in qtubuntu package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  The MainView offered an api to lock the app to portrait. When
  shellRotation landed, that was replaced by entries in the .desktop
  file (X-Ubuntu-Supported-Orientations).

  However, still this isn't really enough for some use cases. For
  example an app might want to be locked to portrait while showing the
  main menu, but when displaying certain content enable allowing
  rotation.

  For that, there would be the need of an API, similar to the .desktop
  entries, but changeable at runtime.

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1413121/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514143] Re: While searching often times the keyboard hides while typing

[Zsombor Egri]

Unfortunately there's no workaround for this. AppHeader has a binding on
enabled, which cannot be worked around. This is indeed a use case we had
not thought enough about. Sorry, we'll fix it ASAP!

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Tim Peeters (tpeeters)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514143

Title:
  While searching often times the keyboard hides while typing

Status in Ubuntu Music App:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  On rc-proposed when searching the keyboard often hides momentarily
  making it possible/likely that the user can accidently select an item
  when they intend to type a letter instead.

  If this is an issue that can not be worked around, potentially an
  acceptable solution would be to wait to filter the items until the
  user stops typing.

  phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 152
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-04 23:03:12
  version version: 152
  version ubuntu: 20151105
  version device: 20150911

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1514143/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1514928] Re: ListItem outside ListView segfaults

[Zsombor Egri]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listitemSelectModeBugs

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1514928

Title:
  ListItem outside ListView segfaults

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Reproduce:
  Use the code from the documentation [1] but add selected: true to any 
ListItem.

  What happens:
  UUITK segfaults

  What should happen:
  It should highlight and not crash

  Stack trace:
  http://pastebin.ubuntu.com/13217004/

  Seems selectedList.contains(-1) segfaults for some reason.

  [1] http://pastebin.ubuntu.com/13217263/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1514928/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1513450] Re: ActivityIndicators cause very high cpu usage for unity8/mir even when visible: false

[Zsombor Egri]

** Project changed: ubuntu-ui-toolkit => ubuntu-ui-toolkit (Ubuntu)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Christian Dywan (kalikiana)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1513450

Title:
  ActivityIndicators cause very high cpu usage for unity8/mir even when
  visible: false

Status in Canonical System Image:
  In Progress
Status in canonical-pocket-desktop:
  New
Status in Mir:
  Invalid
Status in Online Accounts setup for Ubuntu Touch:
  New
Status in linux-flo package in Ubuntu:
  Confirmed
Status in linux-mako package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  running in window mode, open u-s-s, run top
  unity8 running at ~40% cpu on N7 cpu freq ~1GHz

  no monitor attached

  note: testing with silo 18 of mir containing
  lp:~albaguirre/mir/fix-1499039 (equivalent for 0.17)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1513450/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517008] [NEW] Remove DraggingArea in favor of SwipeArea

[Zsombor Egri]

Public bug reported:

DraggingArea is an old implementation for the same thing SwipeArea is
doing, the later actually doing it much better.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Medium
 Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517008

Title:
  Remove DraggingArea in favor of SwipeArea

Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  DraggingArea is an old implementation for the same thing SwipeArea is
  doing, the later actually doing it much better.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1517008/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1368811] Re: [SDK] Bottom edge behaviour needs refining

[Zsombor Egri]

Raised to Critical, should be included in OTA-9

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Medium => Critical

** Tags removed: ota-1
** Tags added: convergence

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/bottomEdge

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1368811

Title:
  [SDK] Bottom edge behaviour needs refining

Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  - Move the bottom edge hint into the SDK so it's behavour is consistent 
across apps, and make the hiding of the bottom edge hint less aggressive.
  - When the user grabs the bottom edge, leave the tab visible until the user 
releases
  - Find a way to make it possible to pull down screens accessed via the bottom 
edge to make the gesture reversible.

  -- UX comment --

  The spec for the bottom edge was updated into the UI toolkit documentation.
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.y7e1o2x66nvr

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1368811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517771] [NEW] Use SwipeArea in BottomEgeHint, remove temporary GestureDetector

[Zsombor Egri]

Public bug reported:

GestureDetector was introduced to temporarily handle touch gesture
detection. Remove this component and base the implementation on recently
landed SwipeArea. Also expose this component as readonly property.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Zsombor Egri (zsombi)
 Status: In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-
toolkit/bottomedgehint_with_swipearea

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517771

Title:
  Use SwipeArea in BottomEgeHint, remove temporary GestureDetector

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  GestureDetector was introduced to temporarily handle touch gesture
  detection. Remove this component and base the implementation on
  recently landed SwipeArea. Also expose this component as readonly
  property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1517771/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517777] [NEW] BottomEdgeHint does not focus when activeFocusOnPress is set

[Zsombor Egri]

Public bug reported:

Set activeFocusOnPressed on BottomEdgeHint. This should result in the
component to take the active focus when clicked with the mouse (status
being Locked or Active), and it doesn't.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Assignee: Zsombor Egri (zsombi)
 Status: In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-
toolkit/bottomedgehint_with_swipearea

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/151

Title:
  BottomEdgeHint does not focus when activeFocusOnPress is set

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Set activeFocusOnPressed on BottomEdgeHint. This should result in the
  component to take the active focus when clicked with the mouse (status
  being Locked or Active), and it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/151/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1368811] Re: [SDK] Bottom edge behaviour needs refining

[Zsombor Egri]

** Changed in: canonical-devices-system-image
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1368811

Title:
  [SDK] Bottom edge behaviour needs refining

Status in Canonical System Image:
  In Progress
Status in Ubuntu UX:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  - Move the bottom edge hint into the SDK so it's behavour is consistent 
across apps, and make the hiding of the bottom edge hint less aggressive.
  - When the user grabs the bottom edge, leave the tab visible until the user 
releases
  - Find a way to make it possible to pull down screens accessed via the bottom 
edge to make the gesture reversible.

  -- UX comment --

  The spec for the bottom edge was updated into the UI toolkit documentation.
  
https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit?pli=1#heading=h.y7e1o2x66nvr

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1368811/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517777] Re: BottomEdgeHint does not focus when activeFocusOnPress is set

[Zsombor Egri]

** Branch unlinked: lp:~zsombi/ubuntu-ui-
toolkit/bottomedgehint_with_swipearea

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/151

Title:
  BottomEdgeHint does not focus when activeFocusOnPress is set

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Set activeFocusOnPressed on BottomEdgeHint. This should result in the
  component to take the active focus when clicked with the mouse (status
  being Locked or Active), and it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/151/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517798] [NEW] Add ability to assign action to BottomEdgeHint

[Zsombor Egri]

Public bug reported:

This requires the BottomEdgeHint to be derived from ActionItem

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Zsombor Egri (zsombi)
 Status: In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-
toolkit/bottomedgehint_with_swipearea

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517798

Title:
  Add ability to assign action to BottomEdgeHint

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  This requires the BottomEdgeHint to be derived from ActionItem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1517798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517614] Re: Page.head.sections.selectedIndex binding of values is broken

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Tim Peeters (tpeeters)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517614

Title:
  Page.head.sections.selectedIndex binding of values is broken

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  When trying to assign a binding value to head.sections.selectedIndex, this 
value is not updated when the bound value changes.
  See the example program below:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  id: mainview
  objectName: "mainView"

  width: units.gu(100)
  height: units.gu(75)

  Page {
  id: mainPage
  title: "selectedIndex: " + head.sections.selectedIndex + " should be: 
" + mainPage.selectedIndex
  property int selectedIndex: -1
  head.sections.model: [ "first", "second", "third" ]
  head.sections.selectedIndex: mainPage.selectedIndex

  Rectangle {
  anchors.fill: parent
  color: "white"

  Label {
  anchors.centerIn: parent
  text: "Click me"
  }
  }

  MouseArea {
  anchors.fill: parent
  onClicked: mainPage.selectedIndex = (mainPage.selectedIndex + 1) 
% 3
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517614/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517612] Re: Page.head.sections selects the first item even though selectedIndex is -1

[Zsombor Egri]

Isn't this similar to bug 1511839?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517612

Title:
  Page.head.sections selects the first item even though selectedIndex is
  -1

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  In some cases it is desired that no header section is selected when
  the program starts. We used to achieve that by setting
  head.sections.selectedIndex to -1, but on Ubuntu.Components 1.3 this
  doesn't work: the first item gets selected by default. See the sample
  program below:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  id: mainview
  objectName: "mainView"

  width: units.gu(100)
  height: units.gu(75)

  Page {
  id: mainPage
  title: "Should not select"
  head.sections.model: [ "first", "second", "third" ]
  head.sections.selectedIndex: -1 
  }
  }

  This is actually a regression, the sample program below works fine on
  Ubuntu.Components 1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1517612/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517771] Re: Use SwipeArea in BottomEgeHint, remove temporary GestureDetector

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517771

Title:
  Use SwipeArea in BottomEgeHint, remove temporary GestureDetector

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  GestureDetector was introduced to temporarily handle touch gesture
  detection. Remove this component and base the implementation on
  recently landed SwipeArea. Also expose this component as readonly
  property.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1517771/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517798] Re: Add ability to assign action to BottomEdgeHint

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1517798

Title:
  Add ability to assign action to BottomEdgeHint

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  This requires the BottomEdgeHint to be derived from ActionItem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1517798/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1517777] Re: BottomEdgeHint does not focus when activeFocusOnPress is set

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/151

Title:
  BottomEdgeHint does not focus when activeFocusOnPress is set

Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

Bug description:
  Set activeFocusOnPressed on BottomEdgeHint. This should result in the
  component to take the active focus when clicked with the mouse (status
  being Locked or Active), and it doesn't.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/151/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500934] Re: The new AdaptivePageLayout should allow replacing primaryPage

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1500934

Title:
  The new AdaptivePageLayout should allow replacing primaryPage

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The new AdaptivePageLayout does not allow replacing of the
  primaryPage.

  Simplest use case:
  primaryPage: isSignedIn ? masterPage : signInPage

  I've explained in more detail in the #sdk channel, it seems I have
  convinced two developers the limitation of not allowing to replace the
  primaryPage now seems arbitrary. Allowing to replace the primaryPage
  makes the component much more flexible.

  Naturally, replacing the primaryPage means all of the pages will be
  removed, as the primary page is like "tree root" in this situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1500934/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1499845] Re: Expose whether an app has a visible BottomEdge

[Zsombor Egri]

The BottomEdge component is decided to be available per Page, that means
that it will be available if the Page is active. Now there can be
situations when more than one BottomEdge will be available at a time,
and the logic described above does not deal with that. Also, the edge
tutorial does not seem to take into account the convergence: I guess it
won't render across the entire screen then, only above the window chrome
:)

For the phone case, I think shell should not even be involved, it's all
about the app itself. Or maybe the only time the shell should be
involved is when requesting a full screen view overlaying the app's
surface. To be honest I do not see the reason to cover the indicator
area, especially if we think the same logic should work on convergence,
i.e window mode.

So, my suggestions:
1) UITK will have the BottomEdge component
2) apps will know when the education view has to be launched and will do so per 
page, but a Tutorial framework (or component) should be provided, preferably by 
the shell
3) the Tutorial component will follow the position if the BottomEdge

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1499845

Title:
  Expose whether an app has a visible BottomEdge

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  == The Design ==

  The edge tutorial that is shown during the first-boot is getting a
  redesign [1].

  As part of it, the bottom edge tutorial screen is intended to only
  appear after a certain amount of time and only if a user is opening or
  switching to an app with a bottom edge to drag up.

  When that happens, a page appears covering the whole screen, pointing
  to the bottom and saying "Swipe from the bottom edge to manage the
  app".  Then when the user does swipe up, it fades out as the bottom is
  swiped.   I've attached a screenshot of an early mockup for this (back
  when it was designed for the App scope, not an actual app).

  Since it must cover the entire screen (and turn off the launcher and
  panel during it), it should probably be rendered by the shell (which
  is rendering the rest of the tutorial anyway).  So we have to
  coordinate between the app and the shell.

  There are two main technical difficulties in implementing this, the
  way I see it.  Detecting if the current page has a valid BottomEdge
  and synchronizing the fade-out with the bottom-edge drag.

  [1] https://docs.google.com/document/d/1pZ-Ro--
  2eaRzjZKNRoYAeDvQHMkCuyvVuPFWFQfPW4s

  == Detecting BottomEdge ==

  We need:
  1) A BottomEdge SDK component
  2) That is enabled
  3) That is attached to the bottom edge of the app
  4) That is currently being rendered (might be in a Page that isn't on top 
right now)
  5) That isn't obscured by some other widget or MouseArea

  #5 is going to be hard to detect in the wild west of apps from the
  store.  But one thing we could do restrict this to known-well-behaved
  apps that are shipped by default anyway.  The user is most likely to
  be in one of those early on in their phone experience anyway.

  Once the SDK can detect this situation, it needs to signal it somehow.
  Maybe the "valid-bottom-edge" state can bubble up to qtmir's
  ApplicationManager and then the shell.  Any ideas on the best way to
  do that?

  == Synchronizing fade transition ==

  I'm thinking there are two ways:

  1) Communicate from the app to the shell how far the bottom edge has
  been dragged, as it is being dragged.  Presumably via the same channel
  as we communicate that there is a valid bottom edge in the first
  place.

  2) Fake it and have the shell track the drag itself.  It then needs to
  mirror the input to the app so that it also receives the drag.

  #2 is probably easier.  Slightly brittle in case for whatever reason
  the app interferes with the drag or does something on its own that
  would desynchronize the animation.  But again, if we limit this to
  well-known apps, we can avoid that.

  == Open tasks ==

  1) Get general feedback on these ideas
  2) Determine how feasible it is for the SDK to detect a valid BottomEdge
  3) Determine the best way to signal that state from the SDK up to the shell
  4) Implement it

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1499845/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500934] Re: The new AdaptivePageLayout should allow replacing primaryPage

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/aplReplacePrimaryPage

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1500934

Title:
  The new AdaptivePageLayout should allow replacing primaryPage

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The new AdaptivePageLayout does not allow replacing of the
  primaryPage.

  Simplest use case:
  primaryPage: isSignedIn ? masterPage : signInPage

  I've explained in more detail in the #sdk channel, it seems I have
  convinced two developers the limitation of not allowing to replace the
  primaryPage now seems arbitrary. Allowing to replace the primaryPage
  makes the component much more flexible.

  Naturally, replacing the primaryPage means all of the pages will be
  removed, as the primary page is like "tree root" in this situation.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1500934/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1495554] Re: AbstractButton 1.3 pressAndHold breaks inside a Loader

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => High

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/abstractbutton_longpress

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1495554

Title:
  AbstractButton 1.3 pressAndHold breaks inside a Loader

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The attached file shows that AbstractButton pressAndHold signal does
  not trigger if inside a Loader with Ubuntu Components 1.3

  It works fine with Ubuntu Components 1.2 and with MouseArea.

  This blocks unity8 moving to 1.3 since breaks the Dash.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495554/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1500118] Re: ListItem feature request: Signal at end of live drag

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listItemDropEvent

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1500118

Title:
  ListItem feature request: Signal at end of live drag

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  When a ListItem is dragged, it emits "Started" and "Moving" events.
  But if each "Moving" event is accepted, as happens in a live drag
  case, no "Dropped" event will be emitted when the item is finally
  dropped.  One should be added.  The "to" and "from" parameters could
  both be set to the final position, or they could be set to an invalid
  value.

  Example use cases:
  1) Updating an underlying data store.  The QML list model may present data 
stored on disk.  (In a database, for instance.)  Updating the model may be 
quick while updating the disk store is slow.  It would be nice to be able to 
give the feedback of the live updates but put off updating the data store until 
the drag is over.  The "Dropped" signal is necessary for this.
  2) Changing styling during drag.  A developer may want to change some styling 
of elements other than the dragged element during the drag.  For instance, 
non-dragged items could be shaded so as to be less prominent, or additional 
information could be presented.  The "Dropped" signal is necessary to know when 
to reset the styles.
  3) Consistency in a mixed drag action.  By choosing which "Moving" events to 
accept, a developer can create a situation in which parts of a drag are live 
and others are not.  Currently, the "Dropped" signal will be emitted for some 
of these drags and not for others.  In addition to being surprising, this may 
complicated clean-up code.  If the "Dropped" signal is always emitted, this 
situation would be simplified.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1500118/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493882] Re: selectMode property isn't obeyed on ListItem if set at component creation

[Zsombor Egri]

Actually you can do that on the ListView's level, using
ViewItems.selectMode property, no need a Component.onCompleted
implementation.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1493882

Title:
  selectMode property isn't obeyed on ListItem if set at component
  creation

Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  Steps to reproduce

  1) Run the following QML:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  selectMode: true
  Label {
  anchors.centerIn: parent
  text: index
  }
  }
  }
  }
  }

  Expected outcome

   ListView should be in selection mode

  Actual outcome

   ListView isn't in selection mode


  This can be worked around by setting the property after the component
  is complete:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  Label {
  anchors.centerIn: parent
  text: index
  }
  Component.onCompleted: {
  selectMode = true
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1493882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493880] Re: ListItem's selectedChanged signal is emitted when the selection hasn't changed

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1493880

Title:
  ListItem's selectedChanged signal is emitted when the selection hasn't
  changed

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Run the following QML:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  onSelectedChanged: {
  console.log("Selected changed for index: " + index + " 
to: " + selected)
  }
  Label {
  anchors.centerIn: parent
  text: index
  }
  Component.onCompleted: {
  selectMode = true
  }
  }
  }
  }
  }

  2) Select item 4

  Expected outcome:

   Terminal should display:
   
  qml: Selected changed for index: 4 to: true

  Actual outcome:

   Terminal actually displays:

  qml: Selected changed for index: 0 to: false
  qml: Selected changed for index: 1 to: false
  qml: Selected changed for index: 2 to: false
  qml: Selected changed for index: 3 to: false
  qml: Selected changed for index: 4 to: true

  Items 0 - 3 haven't changed so shouldn't have their selectedChange
  signal emitted when item 4 changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1493880/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493880] Re: ListItem's selectedChanged signal is emitted when the selection hasn't changed

[Zsombor Egri]

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listitemSelectModeBugs

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1493880

Title:
  ListItem's selectedChanged signal is emitted when the selection hasn't
  changed

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce:

  1) Run the following QML:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  onSelectedChanged: {
  console.log("Selected changed for index: " + index + " 
to: " + selected)
  }
  Label {
  anchors.centerIn: parent
  text: index
  }
  Component.onCompleted: {
  selectMode = true
  }
  }
  }
  }
  }

  2) Select item 4

  Expected outcome:

   Terminal should display:
   
  qml: Selected changed for index: 4 to: true

  Actual outcome:

   Terminal actually displays:

  qml: Selected changed for index: 0 to: false
  qml: Selected changed for index: 1 to: false
  qml: Selected changed for index: 2 to: false
  qml: Selected changed for index: 3 to: false
  qml: Selected changed for index: 4 to: true

  Items 0 - 3 haven't changed so shouldn't have their selectedChange
  signal emitted when item 4 changes.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1493880/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1493882] Re: selectMode property isn't obeyed on ListItem if set at component creation

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/listitemSelectModeBugs

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1493882

Title:
  selectMode property isn't obeyed on ListItem if set at component
  creation

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  Steps to reproduce

  1) Run the following QML:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  selectMode: true
  Label {
  anchors.centerIn: parent
  text: index
  }
  }
  }
  }
  }

  Expected outcome

   ListView should be in selection mode

  Actual outcome

   ListView isn't in selection mode


  This can be worked around by setting the property after the component
  is complete:

  import QtQuick 2.4
  import Ubuntu.Components 1.3

  MainView {
  Page {
  ListView {
  anchors.fill: parent
  model: 5
  delegate: ListItem {
  Label {
  anchors.centerIn: parent
  text: index
  }
  Component.onCompleted: {
  selectMode = true
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1493882/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1501673] Re: [UCLabel] Remove REVISION requirement for textSize property

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1501673

Title:
  [UCLabel] Remove REVISION requirement for textSize property

Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  ListItemLayout has 3 UCLabels inside its main slot.

  Those labels are created on C++ side, and they're exposed to QML via
  Q_PROPERTY.

  Because of the REVISION 1 in textSize Q_PROPERTY definition,
  initializing textSize from QML side on C++ created labels fails with: 

  ".textSize" is not available due to component versioning.

  Here's the testcase: 
  import QtQuick 2.4
  import Ubuntu.Components 1.3
  ListItemLayout {
  title.text: "Hello"
  title.textSize: Label.XLarge
  }

  This is probably a bug in Qt's versioning handling, but since we don't 
actually need the REVISION requirement for textSize,
  we should just drop it to fix the initialization issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1501673/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1503901] Re: Authenticator app won't open with latest SDK

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: Zoltan Balogh (bzoltan) => Zsombor Egri (zsombi)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1503901

Title:
  Authenticator app won't open with latest SDK

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  The Authenticator app in the store won't open on latest rc-proposed
  images.  I'm assuming something in the SDK changed out from under it.
  Nothing useful in the log though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503901/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1503901] Re: Authenticator app won't open with latest SDK

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1503901

Title:
  Authenticator app won't open with latest SDK

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The Authenticator app in the store won't open on latest rc-proposed
  images.  I'm assuming something in the SDK changed out from under it.
  Nothing useful in the log though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503901/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1503901] Re: Authenticator app won't open with latest SDK

[Zsombor Egri]

** Branch unlinked: lp:~zsombi/ubuntu-ui-toolkit/label_child_crash

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1503901

Title:
  Authenticator app won't open with latest SDK

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  In Progress

Bug description:
  The Authenticator app in the store won't open on latest rc-proposed
  images.  I'm assuming something in the SDK changed out from under it.
  Nothing useful in the log though.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1503901/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1451225] Re: Cannot set background colour for overflow of leading/trailing actions

[Zsombor Egri]

The bug here is the colouring of the panel colors using Palette value
rather than setting the bg colour of the panel. Unfortunately we did not
receive any colouring guides from UX for dark themes, only for Ambiance.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1451225

Title:
  Cannot set background colour for overflow of leading/trailing actions

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In music we use dark colours for the listitem background and therefore
  the background of the actions. With the 'new' listitems you can set
  the colour of the action by putting it inside a Rectangle. However I
  have been unable to set the colour if you 'pull' too far, it appears
  as white in this case.

  I have created a mini app here [0], if you open the application and
  drag a listitem to the left you will notice that the action appears,
  with a background colour set, but then if the user pulls too far it
  turns to white. (I assume it is the same with the leading actions if
  you didn't want them to have a red background)

  Is there anyway we can set this colour?

  0 - http://pastebin.ubuntu.com/10979455/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1451225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1451225] Re: Cannot set background colour for overflow of leading/trailing actions

[Zsombor Egri]

The solution is for you to provide your own theme, where you override
the ListItemStyle and set the colour of the trailing panel accordingly.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1451225

Title:
  Cannot set background colour for overflow of leading/trailing actions

Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  In music we use dark colours for the listitem background and therefore
  the background of the actions. With the 'new' listitems you can set
  the colour of the action by putting it inside a Rectangle. However I
  have been unable to set the colour if you 'pull' too far, it appears
  as white in this case.

  I have created a mini app here [0], if you open the application and
  drag a listitem to the left you will notice that the action appears,
  with a background colour set, but then if the user pulls too far it
  turns to white. (I assume it is the same with the leading actions if
  you didn't want them to have a red background)

  Is there anyway we can set this colour?

  0 - http://pastebin.ubuntu.com/10979455/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1451225/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1452676] Re: [SDK] Right-click menu instead of leading/ trailing actions

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
 Assignee: (unassigned) => Zsombor Egri (zsombi)

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: New => Triaged

** Tags added: convergence

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1452676

Title:
  [SDK] Right-click menu instead of leading/ trailing actions

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  On desktops/ laptops the leading and trailing actions of list items
  should be available as context menus. In practise we probably want to
  enable the menu if a mouse is being used and only enable the actions
  if s touchscreen is available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1452676/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1197058] Re: [SDK ListItems] should allow controls on the left

[Zsombor Egri]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in
Ubuntu.
https://bugs.launchpad.net/bugs/1197058

Title:
  [SDK ListItems] should allow controls on the left

Status in Ubuntu UX bugs:
  Triaged
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  Looking to this system settings design:
  
https://wiki.ubuntu.com/Sound?action=AttachFile&do=get&target=phone-settings-sound.png

  The list have list entries with that format
  |  [check]  |

  
  I've used a custom item for those doing that:

  'ListItem.Base {
  property string textEntry: "";
  property bool checkStatus: false;

  Row {
  anchors.top: parent.top
  anchors.bottom: parent.bottom
  spacing: units.gu(2)

  CheckBox {
  anchors.verticalCenter: parent.verticalCenter
  checked: checkStatus
  }
  Label {
  anchors.verticalCenter: parent.verticalCenter
  text: textEntry
  }
  }
  }"

  
  But:
  - that's not standard
  - clicking on the label doesn't tweak the checkbox as it does for other 
controls (I can hack that easily if needed though)
  - the UI might not be consistent with what is used in other place

  This bug might also be a place to discuss if those items are fine to
  use or non coherent with our use of the toolkit in other places...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1197058/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp