[Touch-packages] [Bug 1504755] Re: Popover does not open on top of all other Items in the root item.

[Tim Peeters]

** Summary changed:

- Popover does not open on top of all other Items
+ Popover does not open on top of all other Items in the root item.

-- 
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/1504755

Title:
  Popover does not open on top of all other Items in the root item.

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

Bug description:
  When I open a Popover, I expect it to be on top of all other Items.
  This is not the case if any Item has a z-value > 0, the Popover will
  then open behind that Item, potentially hiding the Popover.

  Use the example code below to reproduce the issue. Run the qml code
  and click the button at the bottom to open the popover behind the blue
  rectangle.

  Note that also the MouseArea in the blue rectangle eats the events of
  the Popover's InverseMouseArea that is used to close the popover. So
  if there is a MouseArea in an Item with z>1, this area cannot be
  clicked to close the Popover.

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Popups 1.3

  Item {
  width: 600
  height: 600

  Rectangle {
  anchors.centerIn: parent
  color: "blue"
  width: 400
  height: 400
  opacity: 0.8
  z: 1
  MouseArea { anchors.fill: parent }
  }
  Rectangle {
  anchors {
  right: parent.right
  verticalCenter: parent.verticalCenter
  }
  width: 300
  height: 300
  color: "yellow"
  }

  Button {
  id: button
  anchors {
  bottom: parent.bottom
  horizontalCenter: parent.horizontalCenter
  margins: 30
  }
  text: "Pop!"
  onClicked: PopupUtils.open(popoverComponent, button)

  Component {
  id: popoverComponent

  Popover {
  Rectangle {
  color: "green"
  width: parent.width
  height: 300
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1504755/+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

[Tim Peeters]

** 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/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:
  In Progress

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 1515593] Re: head.foregroundColor does not affect icons in the header

[Tim Peeters]

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

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

-- 
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:
  In Progress

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 1515593] Re: head.foregroundColor does not affect icons in the header

[Tim Peeters]

** 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/1515593

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

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

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 1514143] Re: While searching often times the keyboard hides while typing

[Tim Peeters]

** 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/1514143

Title:
  While searching often times the keyboard hides while typing

Status in Canonical System Image:
  In Progress
Status in Ubuntu Music App:
  Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Committed

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/canonical-devices-system-image/+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 1432696] Re: [SDK] Bottom edge header improvement

[Tim Peeters]

** 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 messaging-app in Ubuntu.
https://bugs.launchpad.net/bugs/1432696

Title:
  [SDK] Bottom edge header improvement

Status in Dekko:
  Fix Released
Status in Ubuntu Calendar App:
  Invalid
Status in Ubuntu Clock App:
  Fix Released
Status in Ubuntu Document Viewer App:
  Fix Released
Status in Ubuntu UX:
  Fix Committed
Status in address-book-app package in Ubuntu:
  Fix Released
Status in dialer-app package in Ubuntu:
  Confirmed
Status in messaging-app package in Ubuntu:
  Confirmed
Status in ubuntu-clock-app package in Ubuntu:
  Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  When user does a bottom edge gesture to show a new view (Address Book,
  Dialer, Clock, etc) the new header should never have a chevron
  pointing left, as it seems to suggest the wrong direction for the
  movement.

  The header of the new View should always have a chevron pointing down.
  Also, it should allow people using a gesture and dismiss the new
  screen by dragging or swiping the [chevron & title area of the header]
  downward

  UX here:
  
https://www.dropbox.com/s/ypmhej7ie2hrc9a/down_chevron_for_manage_dash_01%28wireframe%29.tiff?dl=0

  VD:
  https://www.dropbox.com/s/1wuihy8tf7no7iw/Music_Down_Chevron.jpg?dl=0

To manage notifications about this bug go to:
https://bugs.launchpad.net/dekko/+bug/1432696/+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

[Tim Peeters]

This construction with a binding for head.sections.selectedIndex should
be avoided, because when the user taps on the sections to change the
current section, the new index of the section is updated and the binding
is broken.

Perhaps your newly defined property int selectedIndex should be an alias
instead?

-- 
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 1517614] Re: Page.head.sections.selectedIndex binding of values is broken

[Tim Peeters]

Right. I confirmed the bug. For some reason the selectedIndex of
head.sections is not updated. The binding seems broken.

I did test with the new header that we have in staging:
http://paste.ubuntu.com/13345460/ and that works fine.

-- 
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 1518002] Re: Header is shown at startup and slides out even though it is set to be invisible and locked

[Tim Peeters]

With the current header configuration using Page.head there is this
issue, and other issues related to the configuration of more customized
header. We introduced a new Page.header property (in UITK staging, soon
to land in trunk) that can be set to any Item to have your own header,
and if you set it to an instance of the new PageHeader component, it
will look the same as the current header. It will require changing some
code (not much) related to the header, but after doing that you will
have a lot more flexibility in what you can do with the header,
including properly hiding/disabling it.

The current API will keep working in UITK 1.3, as long as you don't set
the Page.header property, the old header will appear for your page. But
I will recommend apps to switch to the new header once we have it landed
in an image. The documentation for the header will be included in UITK
docs at the same time the new features land.

** 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/1518002

Title:
  Header is shown at startup and slides out even though it is set to be
  invisible and locked

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

Bug description:
  Some applications have no header on the starting page, but may have
  headers on the sub pages (for settings), eg Calculator, Clock and
  Weather. However it has been observed that if you set the header to
  invisible and locked with the code below, the header is infact shown
  at startup and then slides away (as shown in this video [0]).

  head {
locked: true
visible: false
  }

  
  What happened:
  1) Create an application that uses the code above to have no header on the 
starting page
  2) Deploy and launch the application
  3) Notice that the header is initially shown but then slides away

  What was expected to happen:
  At step 3) for the header not to be shown at startup.

  
  0 - https://www.youtube.com/watch?v=OMqJbc6H6IY

  $ system-image-cli -i
  current build number: 160
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 07:59:01
  version version: 160
  version ubuntu: 20151112.1
  version device: 20150911
  version custom: mako-1.1

  $ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin
  qtdeclarative5-ubuntu-ui-toolkit-plugin:
Installed: 1.3.1705+15.04.20151118-0ubuntu1
Candidate: 1.3.1705+15.04.20151118-0ubuntu1
Version table:
   *** 1.3.1705+15.04.20151118-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   1.2.1458+15.04.20150422-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1518002/+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 1518002] Re: Header is shown at startup and slides out even though it is set to be invisible and locked

[Tim Peeters]

** Tags added: header

-- 
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/1518002

Title:
  Header is shown at startup and slides out even though it is set to be
  invisible and locked

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

Bug description:
  Some applications have no header on the starting page, but may have
  headers on the sub pages (for settings), eg Calculator, Clock and
  Weather. However it has been observed that if you set the header to
  invisible and locked with the code below, the header is infact shown
  at startup and then slides away (as shown in this video [0]).

  head {
locked: true
visible: false
  }

  
  What happened:
  1) Create an application that uses the code above to have no header on the 
starting page
  2) Deploy and launch the application
  3) Notice that the header is initially shown but then slides away

  What was expected to happen:
  At step 3) for the header not to be shown at startup.

  
  0 - https://www.youtube.com/watch?v=OMqJbc6H6IY

  $ system-image-cli -i
  current build number: 160
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2015-11-12 07:59:01
  version version: 160
  version ubuntu: 20151112.1
  version device: 20150911
  version custom: mako-1.1

  $ apt-cache policy qtdeclarative5-ubuntu-ui-toolkit-plugin
  qtdeclarative5-ubuntu-ui-toolkit-plugin:
Installed: 1.3.1705+15.04.20151118-0ubuntu1
Candidate: 1.3.1705+15.04.20151118-0ubuntu1
Version table:
   *** 1.3.1705+15.04.20151118-0ubuntu1 0
 1001 
http://ppa.launchpad.net/ci-train-ppa-service/stable-phone-overlay/ubuntu/ 
vivid/main armhf Packages
  100 /var/lib/dpkg/status
   1.2.1458+15.04.20150422-0ubuntu1 0
  500 http://ports.ubuntu.com/ubuntu-ports/ vivid/main armhf Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1518002/+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 1518106] Re: Using "$ source export_modules_dir.sh" causes the error "bash: /bin/build_paths.inc: No such file or directory"

[Tim Peeters]

build_paths.inc does not exist until you run 'qmake'. Did you do that?

Also exporting the modules dir before running 'make' to compile the
plugin is useless, so you need to do that as wel.

-- 
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/1518106

Title:
  Using "$ source export_modules_dir.sh" causes the error "bash:
  /bin/build_paths.inc: No such file or directory"

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

Bug description:
  When branching lp:ubuntu-ui-toolkit and using the script
  export_modules_dir.sh it causes the error "bash: /bin/build_paths.inc:
  No such file or directory".

  What happened:
  1) Branch lp:ubuntu-ui-toolkit and cd into the directory
  2) Run the command $ source export_modules_dir.sh
  3) Observe the error "bash: /bin/build_paths.inc: No such file or directory"

  What I expected to happen:
  At step 3) for the modules to be correctly exported.

  
  Note that the workaround I currently perform is running the following set of 
commands (the only difference from the script is ". `dirname 
$0`/build_paths.inc" is now ". build_paths.inc")

  $ . build_paths.inc 
  $ export QML_IMPORT_PATH=$BUILD_DIR/qml
  $ export QML2_IMPORT_PATH=$BUILD_DIR/qml
  $ export UBUNTU_UI_TOOLKIT_THEMES_PATH=$BUILD_DIR/qml
  $ /sbin/initctl set-env --global QML_IMPORT_PATH=$BUILD_DIR/qml
  $ /sbin/initctl set-env --global QML2_IMPORT_PATH=$BUILD_DIR/qml
  $ /sbin/initctl set-env --global UBUNTU_UI_TOOLKIT_THEMES_PATH=$BUILD_DIR/qml

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1518106/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground

[Tim Peeters]

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

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

** 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/1500483

Title:
  [sdk] animate header component when app comes back to the foreground

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

Bug description:
  When the header is hidden by scrolling it out of the view in an app,
  and the user switches between apps, when an app comes back to the
  foreground, the header instantly appears again. This means when going
  back to a previous app, the app is not in exactly the same state as
  where the user left it.

  Example:
  - Open gallery-app
  - Scroll down to hide the header (you need to have enough photos in the 
gallery to scroll down).
  - Long left/right edge swipe to hide send the gallery-app to the background
  - Re-open the gallery app

  Result:
  The gallery-app re-opens with the header visible.

  This can be confusing for the user.
  Two possible solutions:
  1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
  2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

  After discussing with Olga, we decided to go for solution 1. The
  header will show, but it must animate.

  
  -- UX comment -

  As described above: 
  The header should animate once user navigates back to the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1465048] Re: PageHeadSections does not scroll

[Tim Peeters]

The header uses the Sections component, so that is the one that needs to
scroll. I assigned this to myself now, but there other header-related
things that need to be finished first.

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

** Summary changed:

- PageHeadSections does not scroll
+ Sections does not scroll

-- 
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/1465048

Title:
  Sections does not scroll

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

Bug description:
  If there are too many parts in PageHeadSections, there is no way to
  select sections off the screen. This could be solved by allowing the
  sections to be scrolled horizontally, similarly to how the original
  Header worked in the early toolkit versions.

  Example of where this is a problem:
I use the PageHeadSections to allow the user to select between languages 
for translation. The available languages here are set by the user in the 
settings. So, in most cases only 2-5 languages will be listed, but a user could 
decide to use all ~150 languages if they wanted to.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1465048/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground

[Tim Peeters]

** 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/1500483

Title:
  [sdk] animate header component when app comes back to the foreground

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

Bug description:
  When the header is hidden by scrolling it out of the view in an app,
  and the user switches between apps, when an app comes back to the
  foreground, the header instantly appears again. This means when going
  back to a previous app, the app is not in exactly the same state as
  where the user left it.

  Example:
  - Open gallery-app
  - Scroll down to hide the header (you need to have enough photos in the 
gallery to scroll down).
  - Long left/right edge swipe to hide send the gallery-app to the background
  - Re-open the gallery app

  Result:
  The gallery-app re-opens with the header visible.

  This can be confusing for the user.
  Two possible solutions:
  1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
  2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

  After discussing with Olga, we decided to go for solution 1. The
  header will show, but it must animate.

  
  -- UX comment -

  As described above: 
  The header should animate once user navigates back to the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1492328] Re: header icon color should match title label color when backgroundColor is set

[Tim Peeters]

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

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

-- 
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/1492328

Title:
  header icon color should match title label color when backgroundColor
  is set

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

Bug description:
  If I set a custom background color on a MainView, the color of the
  title label in the header is computed to make the title readable, but
  the color of the header icons isn’t, and it may be difficult to see
  them.

  See the attached standalone reproducer, where the background color is
  green, the title is white (white on green is fairly readable), but the
  header icon is the default light grey, which makes it very hard to
  view on the green background. I would expect the icon to be white too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1492328/+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

[Tim Peeters]

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

** 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/1368811

Title:
  [SDK] Bottom edge behaviour needs refining

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

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.

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 1445016] Re: Having access to the page header component would be useful

[Tim Peeters]

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

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

** 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/1445016

Title:
  Having access to the page header component would be useful

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

Bug description:
  Using vivid, currently the pagestack/page try to be smart with the
  header and adjust margins as needed, but that doesn't always work and
  it would be nice to have access to the header component to be able to
  e.g anchor on header.bottom

  small testcase example attached, the intend is to center the label but
  it's not easy to do (you can do it by tweaking the topMargin though)

  (note that the code is inspired from the system settings updates panel
  and bug #1429280)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1445016/+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 1350893] Re: [sdk] Allow header background customization per page

[Tim Peeters]

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

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

** Changed in: ubuntu-ui-toolkit
   Importance: Low => Medium

** 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/1350893

Title:
  [sdk] Allow header background customization per page

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

Bug description:
  Each Page should have the ability to customize a few things about the
  look of the header, these changes should take affect when the page
  becomes the top page in a PageStack or the current tab in Tabs.

  headerColor: Set the background color of the Header
  headerGradient: Same as headerColor, only using a Gradient object instead of 
a single color
  headerImage: Set a background Image on the Header, resized to fit based on 
fillMode
  headerBorderImage: Same as headerImage, but using a BorderImage

  follow-up of this bug: https://bugs.launchpad.net/ubuntu-ui-
  toolkit/+bug/1315884 which I changed to only include header foreground
  color customization.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1350893/+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 1504755] [NEW] Popover does not open on top of all other Items

[Tim Peeters]

Public bug reported:

When I open a Popover, I expect it to be on top of all other Items. This
is not the case if any Item has a z-value > 0, the Popover will then
open behind that Item, potentially hiding the Popover.

Use the example code below to reproduce the issue. Run the qml code and
click the button at the bottom to open the popover behind the blue
rectangle.

Note that also the MouseArea in the blue rectangle eats the events of
the Popover's InverseMouseArea that is used to close the popover. So if
there is a MouseArea in an Item with z>1, this area cannot be clicked to
close the Popover.

import QtQuick 2.4
import Ubuntu.Components 1.3
import Ubuntu.Components.Popups 1.3

Item {
width: 600
height: 600

Rectangle {
anchors.centerIn: parent
color: "blue"
width: 400
height: 400
opacity: 0.8
z: 1
MouseArea { anchors.fill: parent }
}
Rectangle {
anchors {
right: parent.right
verticalCenter: parent.verticalCenter
}
width: 300
height: 300
color: "yellow"
}

Button {
id: button
anchors {
bottom: parent.bottom
horizontalCenter: parent.horizontalCenter
margins: 30
}
text: "Pop!"
onClicked: PopupUtils.open(popoverComponent, button)

Component {
id: popoverComponent

Popover {
Rectangle {
color: "green"
width: parent.width
height: 300
}
}
}
}
}

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Status: New

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

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

** Description changed:

  When I open a Popover, I expect it to be on top of all other Items. This
  is not the case if any Item has a z-value > 0, the Popover will then
  open behind that Item, potentially hiding the Popover.
  
  Use the example code below to reproduce the issue. Run the qml code and
  click the button at the bottom to open the popover behind the blue
  rectangle.
  
  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Popups 1.3
  
  Item {
- width: 600
- height: 600
+ width: 600
+ height: 600
  
- Rectangle {
- anchors.centerIn: parent
- color: "blue"
- width: 400
- height: 400
- opacity: 0.8
- z: 1
- }
- Rectangle {
- anchors {
- right: parent.right
- verticalCenter: parent.verticalCenter
- }
- width: 300
- height: 300
- color: "yellow"
- }
+ Rectangle {
+ anchors.centerIn: parent
+ color: "blue"
+ width: 400
+ height: 400
+ opacity: 0.8
+ z: 1
+ MouseArea { anchors.fill: parent }
+ }
+ Rectangle {
+ anchors {
+ right: parent.right
+ verticalCenter: parent.verticalCenter
+ }
+ width: 300
+ height: 300
+ color: "yellow"
+ }
  
- Button {
- id: button
- anchors {
- bottom: parent.bottom
- horizontalCenter: parent.horizontalCenter
- margins: 30
- }
- text: "Pop!"
- onClicked: PopupUtils.open(popoverComponent, button)
+ Button {
+ id: button
+ anchors {
+ bottom: parent.bottom
+ horizontalCenter: parent.horizontalCenter
+ margins: 30
+ }
+ text: "Pop!"
+ onClicked: PopupUtils.open(popoverComponent, button)
  
- Component {
- id: popoverComponent
+ Component {
+ id: popoverComponent
  
- Popover {
- Rectangle {
- color: "green"
- width: parent.width
- height: 300
- }
- }
- }
- }
+ Popover {
+ Rectangle {
+ color: "green"
+ width: parent.width
+ height: 300
+ }
+ }
+ }
+ }
  }

** Description changed:

  When I open a Popover, I expect it to be on top of all other Items. This
  is not the case if any Item has a z-value > 0, the Popover will then
  open behind that Item, potentially hiding the Popover.
  
  Use the example code below to reproduce the issue. Run the qml code and
  click the button at the bottom to open the popover behind the blue
  rectangle.
+ 
+ Note that also the MouseArea in the blue rectangle eats the events of
+ the Popover's InverseMouseArea that is used to close the popover. So if
+ there is a MouseArea in an Item with z>1, this area cannot be clicked to
+ close the Popover.
  
  import QtQuick 2.4
  imp

[Touch-packages] [Bug 1504755] Re: Popover does not open on top of all other Items

[Tim Peeters]

The problem only occurs when the parent of the item with z>0 is actually
the root item. The popover foreground is not reparented there because it
is already having that Item as its parent.

-- 
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/1504755

Title:
  Popover does not open on top of all other Items

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

Bug description:
  When I open a Popover, I expect it to be on top of all other Items.
  This is not the case if any Item has a z-value > 0, the Popover will
  then open behind that Item, potentially hiding the Popover.

  Use the example code below to reproduce the issue. Run the qml code
  and click the button at the bottom to open the popover behind the blue
  rectangle.

  Note that also the MouseArea in the blue rectangle eats the events of
  the Popover's InverseMouseArea that is used to close the popover. So
  if there is a MouseArea in an Item with z>1, this area cannot be
  clicked to close the Popover.

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Popups 1.3

  Item {
  width: 600
  height: 600

  Rectangle {
  anchors.centerIn: parent
  color: "blue"
  width: 400
  height: 400
  opacity: 0.8
  z: 1
  MouseArea { anchors.fill: parent }
  }
  Rectangle {
  anchors {
  right: parent.right
  verticalCenter: parent.verticalCenter
  }
  width: 300
  height: 300
  color: "yellow"
  }

  Button {
  id: button
  anchors {
  bottom: parent.bottom
  horizontalCenter: parent.horizontalCenter
  margins: 30
  }
  text: "Pop!"
  onClicked: PopupUtils.open(popoverComponent, button)

  Component {
  id: popoverComponent

  Popover {
  Rectangle {
  color: "green"
  width: parent.width
  height: 300
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1504755/+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 1504755] Re: Popover does not open on top of all other Items

[Tim Peeters]

So, wrapping another Item around the example code above which serves as
the root item, the problem is not there. Also, when the root Item is a
MainView, the problem does not occur because the MainView  places its
children in a separate default Item.

This makes the bug less urgent for now.

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

-- 
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/1504755

Title:
  Popover does not open on top of all other Items

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

Bug description:
  When I open a Popover, I expect it to be on top of all other Items.
  This is not the case if any Item has a z-value > 0, the Popover will
  then open behind that Item, potentially hiding the Popover.

  Use the example code below to reproduce the issue. Run the qml code
  and click the button at the bottom to open the popover behind the blue
  rectangle.

  Note that also the MouseArea in the blue rectangle eats the events of
  the Popover's InverseMouseArea that is used to close the popover. So
  if there is a MouseArea in an Item with z>1, this area cannot be
  clicked to close the Popover.

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Popups 1.3

  Item {
  width: 600
  height: 600

  Rectangle {
  anchors.centerIn: parent
  color: "blue"
  width: 400
  height: 400
  opacity: 0.8
  z: 1
  MouseArea { anchors.fill: parent }
  }
  Rectangle {
  anchors {
  right: parent.right
  verticalCenter: parent.verticalCenter
  }
  width: 300
  height: 300
  color: "yellow"
  }

  Button {
  id: button
  anchors {
  bottom: parent.bottom
  horizontalCenter: parent.horizontalCenter
  margins: 30
  }
  text: "Pop!"
  onClicked: PopupUtils.open(popoverComponent, button)

  Component {
  id: popoverComponent

  Popover {
  Rectangle {
  color: "green"
  width: parent.width
  height: 300
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1504755/+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 1504755] Re: Popover does not open on top of all other Items

[Tim Peeters]

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

-- 
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/1504755

Title:
  Popover does not open on top of all other Items

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

Bug description:
  When I open a Popover, I expect it to be on top of all other Items.
  This is not the case if any Item has a z-value > 0, the Popover will
  then open behind that Item, potentially hiding the Popover.

  Use the example code below to reproduce the issue. Run the qml code
  and click the button at the bottom to open the popover behind the blue
  rectangle.

  Note that also the MouseArea in the blue rectangle eats the events of
  the Popover's InverseMouseArea that is used to close the popover. So
  if there is a MouseArea in an Item with z>1, this area cannot be
  clicked to close the Popover.

  import QtQuick 2.4
  import Ubuntu.Components 1.3
  import Ubuntu.Components.Popups 1.3

  Item {
  width: 600
  height: 600

  Rectangle {
  anchors.centerIn: parent
  color: "blue"
  width: 400
  height: 400
  opacity: 0.8
  z: 1
  MouseArea { anchors.fill: parent }
  }
  Rectangle {
  anchors {
  right: parent.right
  verticalCenter: parent.verticalCenter
  }
  width: 300
  height: 300
  color: "yellow"
  }

  Button {
  id: button
  anchors {
  bottom: parent.bottom
  horizontalCenter: parent.horizontalCenter
  margins: 30
  }
  text: "Pop!"
  onClicked: PopupUtils.open(popoverComponent, button)

  Component {
  id: popoverComponent

  Popover {
  Rectangle {
  color: "green"
  width: parent.width
  height: 300
  }
  }
  }
  }
  }

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1504755/+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

[Tim Peeters]

The ListItem itself supports dragging left or right to show leading and
trailing actions. This would conflict with the possibility of dragging
ListItem contents independently. If you do not need that ListItem
functionality, I would say use a simple Item as a delegate instead of a
ListItem.

-- 
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:
  New

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 1487414] Re: recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

[Tim Peeters]

Either this, or disable recording when recordmydesktop is not found (but
add it to Suggested dependencies).

-- 
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/1487414

Title:
  recordmydesktop should be a dependency of ubuntu-ui-toolkit-autopilot

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

Bug description:
  Attempting to debug an issue with local test runs I removed
  recordmydesktop (as it was spiking at 100% CPU and tests got stuck)
  and it turns out I could no longer run tests - yet it's not a
  dependency of ubuntu-ui-toolkit-autopilot.

  Error: The application 'recordmydesktop' needs to be installed to
  record failing jobs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1487414/+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 1495408] Re: Black square in header

[Tim Peeters]

** 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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1498863] Re: Scenarios in ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page fail with autopilot.exceptions.StateNotFoundError

[Tim Peeters]

** 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/1498863

Title:
  Scenarios in
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page
  fail with autopilot.exceptions.StateNotFoundError

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

Bug description:
  Some of the scenarios
  ubuntuuitoolkit.tests.gallery.test_gallery.OpenPagesTestCase.test_open_page
  in fail with the following error:

  autopilot.exceptions.StateNotFoundError: Object not found with name
  '*' and properties {'objectName': 'header_title_label', 'text':
  'Pickers'}

  As can be seen in all of these cases the page is being selected but
  only rendered with considerable delay, causing AutoPilot to try
  selecting the object too early.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1498863/+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 1500483] Re: [sdk] animate header component when app comes back to the foreground

[Tim Peeters]

** 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/1500483

Title:
  [sdk] animate header component when app comes back to the foreground

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

Bug description:
  When the header is hidden by scrolling it out of the view in an app,
  and the user switches between apps, when an app comes back to the
  foreground, the header instantly appears again. This means when going
  back to a previous app, the app is not in exactly the same state as
  where the user left it.

  Example:
  - Open gallery-app
  - Scroll down to hide the header (you need to have enough photos in the 
gallery to scroll down).
  - Long left/right edge swipe to hide send the gallery-app to the background
  - Re-open the gallery app

  Result:
  The gallery-app re-opens with the header visible.

  This can be confusing for the user.
  Two possible solutions:
  1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
  2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

  After discussing with Olga, we decided to go for solution 1. The
  header will show, but it must animate.

  
  -- UX comment -

  As described above: 
  The header should animate once user navigates back to the app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1408015] Re: [sdk][UX] Confirmation in the header bar confusing

[Tim Peeters]

New designs are coming which makes this more clear.

** Changed in: ubuntu-ux
   Status: Fix Committed => 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/1408015

Title:
  [sdk][UX] Confirmation in the header bar confusing

Status in Quick Memo:
  New
Status in Ubuntu Calendar App:
  New
Status in Ubuntu Clock App:
  Fix Released
Status in Ubuntu UX:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Imagine a form of some sort, you fill a few fields of data top-down,
  and at the end of it you need to tap in the header at the top to
  save/confirm.

  Pair that with the header going off-screen to leave more screen for
  the content, you have to pull the header in first (and you need to
  know that's where the button will be).

  An example of this behaviour is the calendar app when adding/editing
  an event. One other example (although that could be improved easily by
  auto-saving the new note as soon as it's edited) is the Quick Memo
  app, where when you create a note in the first place you need to tap
  the ✓ icon, but when you're editing, it's all auto-saved and you need
  to tap 〈 to go back to the list of notes.

  I feel like we need to at least come up with clear guidance on what
  belongs in the header, and where a footer with buttons should be used
  (we have a way to stick something on top of the keyboard after all¹).

  http://developer.ubuntu.com/api/qml/sdk-1.0/Ubuntu.Components.MainView
  /#anchorToKeyboard-prop

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 
1.1.1364+15.04.20141209-0ubuntu2
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.15-0ubuntu3
  Architecture: armhf
  Date: Tue Jan  6 17:03:54 2015
  InstallationDate: Installed on 2014-12-17 (20 days ago)
  InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf 
(20141217-020204)
  SourcePackage: ubuntu-ui-toolkit
  UpgradeStatus: No upgrade log present (probably fresh install)

  --- UX comment & resolution --

  The back button in the header should never be used as a confirmation but can 
mean CANCEL and not just BACK.
  If an action or any alterations within the content/screen have to be 
confirmed/saved then it requires a visible call to action. This call to action 
sits by default in the header unless differently specified by 
designer/developer.

  In all here described cases the UX can be improved easily by adding
  clarity to the UI and sometimes just adding a call to action.

  The header can be fixed or can go off-screen the specification for
  that lies with the designer/developer. This means if I have an
  important action in the header which I want to present to the user all
  the time, then the header stays fixed, even if the content is
  scrolled.

  Clock app:
  When creating a new alarm by swiping from the bottom of the screen, the tick 
(confirmation) icon should be disabled. Only after interacting with the screen, 
by changing one of the parameters for example, the tick should be enabled. This 
will signal to user that there was a change and this needs to be confirmed. 
Even more informative is a simple word instead of the tick: SAVE. The SAVE 
option is a new addition to the header and wasn't available so far.
  This concept is already documented in the UI - Toolkit spec which is at the 
bottom of this post. If user taps back before saving then the alarm won't be 
created. Additionally there can be visual feedback by adding the "feedback 
bubble" to the UI.
  If the user taps back before saving the feedback bubble states, e.g. "Alarm 
not saved". If the tick icon is tapped, it can state "Alarm saved" (see 
Notification spec).
  In the Repeat section the select all icon has to move one to the left and a 
tick or "save added". The behaviour will then follow as described above.

  Note app:
  There is nothing wrong with the note app approach but it is a custom made 
behaviour which is up to the developer. This person decided not to use our 
pattern and include a tick or SAVE into the header. There are many note taking 
apps on iOS which are not using their patterns either. This doesn't mean they 
are bad, they just work differently.

  While it is ok to use a "Send Order" or a NEXT at the end of a form,
  for some instances and apps it won't be efficient. This means <
  CANCEL/BACK and CONFIRM (tick/save/done) can sit in the header but it
  is not possible to control apps which don't want to user out UI-
  Toolkit, hence the other solutions will exist too.

  We are constantly improving the UI-Toolit and I will add the
  footer/toolbar idea to potential new projects for design.

  Please see for reference the notification spec:
  
https://docs.google.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit?pli=1#

  Please see for reference the UI

[Touch-packages] [Bug 1445580] Re: Impossible to end a call after switching to airplane mode

[Tim Peeters]

I just experienced the same with image r22, 20150508 on the bq ubuntu
phone.

In the middle of a phone call, where I was holding the phone to my ear
(so interaction should be blocked), the phone call finished (I could not
hear the person at the other end of the line speaking any more), but
pushing the hang-up button did not do anything.

I rebooted the phone, and both sim cards were not detected and then I
saw that flight mode was on. After switching off flight mode I needed
another reboot to get it to work again.

So there are two issues here:
1. Interaction was not blocked while I was in a phone call
2. Dialer app does not detect that flight mode gets enabled and the sim card is 
disabled.


Since then I have been trying to see if the proximity sensor works properly 
while in a phone call. Once I managed to push the hang-up button while the 
phone was on my ear (I couldn't see if the screen was on or off). But 
afterwards I have been testing and the proximity sensor seems fine now, the 
screen turns off and does not respond to touch when I hold my finger (or ear) 
close to the camera.

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

Title:
  Impossible to end a call after switching to airplane mode

Status in the base for Ubuntu mobile products:
  In Progress
Status in dialer-app package in Ubuntu:
  Incomplete
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  As I described here
  https://lists.launchpad.net/ubuntu-phone/msg12177.html
  I accidentally switched the phone to the airplane mode while having an active 
incoming call. As a result it is impossible to end a call - the red button does 
not end the call.

  The bug is easy to reproduce:
  1. Make a call to your Ubuntu phone and answer it.
  2. Switch on 'airplane mode'
  3. As a result you get unusable phone.

  Of course switching gsm off while having an active call is not a
  typical use of the phone, but still the phone should react to this
  situation differently.

  Another thing is that I somehow switched gsm off while holding my
  phone to my ear (which may suggest some issue with the top panel) -
  but I don't know how to reproduce this, hence currently I treat this
  as an very unfortunate accident.

  Workaround for ending the call: make another incoming call to your
  phone.

  BQ (r21)

  : "When you turn on
  Flight Mode: 1. If a phone or Voip call is in progress, an alert
  should appear, “Turning on Flight Mode will end your call.”, with
  buttons “Cancel” and “End Call”. The alert should close automatically
  if the call finishes by itself."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+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 1445580] Re: Impossible to end a call after switching to airplane mode

[Tim Peeters]

So issue 2 of my previous comment is what is being tracked in this bug.
For issue 1, I reported a new bug:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1454845

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

Title:
  Impossible to end a call after switching to airplane mode

Status in the base for Ubuntu mobile products:
  In Progress
Status in dialer-app package in Ubuntu:
  Incomplete
Status in indicator-network package in Ubuntu:
  Triaged
Status in ofono package in Ubuntu:
  Fix Committed
Status in telephony-service package in Ubuntu:
  Invalid

Bug description:
  As I described here
  https://lists.launchpad.net/ubuntu-phone/msg12177.html
  I accidentally switched the phone to the airplane mode while having an active 
incoming call. As a result it is impossible to end a call - the red button does 
not end the call.

  The bug is easy to reproduce:
  1. Make a call to your Ubuntu phone and answer it.
  2. Switch on 'airplane mode'
  3. As a result you get unusable phone.

  Of course switching gsm off while having an active call is not a
  typical use of the phone, but still the phone should react to this
  situation differently.

  Another thing is that I somehow switched gsm off while holding my
  phone to my ear (which may suggest some issue with the top panel) -
  but I don't know how to reproduce this, hence currently I treat this
  as an very unfortunate accident.

  Workaround for ending the call: make another incoming call to your
  phone.

  BQ (r21)

  : "When you turn on
  Flight Mode: 1. If a phone or Voip call is in progress, an alert
  should appear, “Turning on Flight Mode will end your call.”, with
  buttons “Cancel” and “End Call”. The alert should close automatically
  if the call finishes by itself."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580/+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 1454845] [NEW] Touchscreen not disabled during phone call

[Tim Peeters]

Public bug reported:

In the middle of a phone call, where I was holding the phone to my ear
(so interaction should be blocked), the phone call finished (I could not
hear the person at the other end of the line speaking any more), but
pushing the hang-up button did not do anything.

I rebooted the phone, and both sim cards were not detected and then I
saw that flight mode was on. After switching off flight mode I needed
another reboot to get it to work again.

What I think that happened was that during the phone call, I used the
top-dropdown-menu with my ear to enable flight mode.

So there are two issues here:
1. Interaction was not blocked while I was in a phone call
2. Dialer app does not detect that flight mode gets enabled and the sim card is 
disabled (this is already being tracked here 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580 )

Since then I have been trying to see if the proximity sensor works
properly while in a phone call. Once I managed to push the hang-up
button while the phone was on my ear (I couldn't see if the screen was
on or off). But afterwards I have been testing and the proximity sensor
seems fine now, the screen turns off and does not respond to touch when
I hold my finger (or ear) close to the camera.

** Affects: telepathy-ofono (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Touchscreen not disabled during phone call

Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  In the middle of a phone call, where I was holding the phone to my ear
  (so interaction should be blocked), the phone call finished (I could
  not hear the person at the other end of the line speaking any more),
  but pushing the hang-up button did not do anything.

  I rebooted the phone, and both sim cards were not detected and then I
  saw that flight mode was on. After switching off flight mode I needed
  another reboot to get it to work again.

  What I think that happened was that during the phone call, I used the
  top-dropdown-menu with my ear to enable flight mode.

  So there are two issues here:
  1. Interaction was not blocked while I was in a phone call
  2. Dialer app does not detect that flight mode gets enabled and the sim card 
is disabled (this is already being tracked here 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580 )

  Since then I have been trying to see if the proximity sensor works
  properly while in a phone call. Once I managed to push the hang-up
  button while the phone was on my ear (I couldn't see if the screen was
  on or off). But afterwards I have been testing and the proximity
  sensor seems fine now, the screen turns off and does not respond to
  touch when I hold my finger (or ear) close to the camera.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1454845/+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 1454845] Re: Touchscreen not disabled during phone call

[Tim Peeters]

In the second part of this bug description: https://bugs.launchpad.net
/canonical-devices-system-image/+bug/1445580 it is also said that
probably the gsm was switched off while the touchscreen should be
disabled: "Another thing is that I somehow switched gsm off while
holding my phone to my ear (which may suggest some issue with the top
panel) - but I don't know how to reproduce this, hence currently I treat
this as an very unfortunate accident."

But since the other bug is about a different issue, I reported this as a
separate bug about disabling the touchscreen.

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

Title:
  Touchscreen not disabled during phone call

Status in telepathy-ofono package in Ubuntu:
  New

Bug description:
  In the middle of a phone call, where I was holding the phone to my ear
  (so interaction should be blocked), the phone call finished (I could
  not hear the person at the other end of the line speaking any more),
  but pushing the hang-up button did not do anything.

  I rebooted the phone, and both sim cards were not detected and then I
  saw that flight mode was on. After switching off flight mode I needed
  another reboot to get it to work again.

  What I think that happened was that during the phone call, I used the
  top-dropdown-menu with my ear to enable flight mode.

  So there are two issues here:
  1. Interaction was not blocked while I was in a phone call
  2. Dialer app does not detect that flight mode gets enabled and the sim card 
is disabled (this is already being tracked here 
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445580 )

  Since then I have been trying to see if the proximity sensor works
  properly while in a phone call. Once I managed to push the hang-up
  button while the phone was on my ear (I couldn't see if the screen was
  on or off). But afterwards I have been testing and the proximity
  sensor seems fine now, the screen turns off and does not respond to
  touch when I hold my finger (or ear) close to the camera.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-ofono/+bug/1454845/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

Will try to reproduce on vivid.

** 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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

I did not manage to reproduce this on a utopic image.

-- 
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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

** 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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

** 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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

The bug was introduced in lp:ubuntu-ui-toolkit/staging r1438 (in r1437
the bug is not present).

-- 
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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1455406] Re: Search history popover displaced when OSK opens

[Tim Peeters]

Appears to be caused by these changes:
https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/langing-
popoverfix/+merge/252066

-- 
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/1455406

Title:
  Search history popover displaced when OSK opens

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

Bug description:
  With a vivid based image, do a search in the dash. Clear it, start a
  second one (the popover should appear). When the OSK comes up, the
  popver is displaced, being partly off-screen, and covering the input
  field.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1455406/+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 1456205] [NEW] unit test for ActionSelectionPopover is not complete

[Tim Peeters]

Public bug reported:

The unit test for ActionSelectionPopover only checks the default value
of properties. It does not open an ActionSelectionPopover and verify
that clicking an option in the popover will trigger the desired action.
These tests should be added.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Low
 Status: Confirmed

** 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/1456205

Title:
  unit test for ActionSelectionPopover is not complete

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

Bug description:
  The unit test for ActionSelectionPopover only checks the default value
  of properties. It does not open an ActionSelectionPopover and verify
  that clicking an option in the popover will trigger the desired
  action. These tests should be added.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1456205/+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 1456350] [NEW] Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme deprecation notes

[Tim Peeters]

Public bug reported:

We should not be printing these warnings in UITK <= 1.2 because there
using 'Theme' instead of 'theme' is a valid way of doing stuff.

Also it slows down the app because it prints hundreds of these warnings
some times.

For example, running this on device results in OK:
SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntu_system_settings.tests.test_about.StorageTestCase.test_disk

but when I leave out the 'SUPPRESS_DEPRECATED_NOTE=yes', the test fails.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Critical
 Status: New

** Description changed:

  We should not be printing these warnings in UITK <= 1.2 because there
- using Theme is a valid way of doing stuff.
+ using 'Theme' instead of 'theme' is a valid way of doing stuff.
  
- Also it slows down running the app a lot because it prints hundreds of
- these warnings some times.
- 
+ Also it slows down the app because it prints hundreds of these warnings
+ some times.
  
  For example, running this on device results in OK:
  SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntu_system_settings.tests.test_about.StorageTestCase.test_disk
  
- but when I leave out the SUPPRESS_DEPRECATED_NOTE, the test fails.
+ but when I leave out the 'SUPPRESS_DEPRECATED_NOTE=yes', the test fails.

-- 
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/1456350

Title:
  Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme
  deprecation notes

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

Bug description:
  We should not be printing these warnings in UITK <= 1.2 because there
  using 'Theme' instead of 'theme' is a valid way of doing stuff.

  Also it slows down the app because it prints hundreds of these
  warnings some times.

  For example, running this on device results in OK:
  SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntu_system_settings.tests.test_about.StorageTestCase.test_disk

  but when I leave out the 'SUPPRESS_DEPRECATED_NOTE=yes', the test
  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1456350/+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 1456350] Re: Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme deprecation notes

[Tim Peeters]

phablet@ubuntu-phablet:~$ SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run
ubuntu_system_settings.tests.test_about.StorageTestCase

Loading tests from: /usr/lib/python3/dist-packages

Tests running...

Ran 9 tests in 265.605s
OK
phablet@ubuntu-phablet:~$ 



HURRAY \o/

-- 
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/1456350

Title:
  Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme
  deprecation notes

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

Bug description:
  We should not be printing these warnings in UITK <= 1.2 because there
  using 'Theme' instead of 'theme' is a valid way of doing stuff.

  Also it slows down the app because it prints hundreds of these
  warnings some times.

  For example, running this on device results in OK:
  SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntu_system_settings.tests.test_about.StorageTestCase.test_disk

  but when I leave out the 'SUPPRESS_DEPRECATED_NOTE=yes', the test
  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1456350/+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 1456350] Re: Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme deprecation notes

[Tim Peeters]

*** This bug is a duplicate of bug 1454281 ***
https://bugs.launchpad.net/bugs/1454281

** This bug has been marked a duplicate of bug 1454281
   Ridiculous amount of warning spam with non-1.3 code

-- 
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/1456350

Title:
  Apps importing UITK 1.2 or older print a lot of UCDeprecatedTheme
  deprecation notes

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

Bug description:
  We should not be printing these warnings in UITK <= 1.2 because there
  using 'Theme' instead of 'theme' is a valid way of doing stuff.

  Also it slows down the app because it prints hundreds of these
  warnings some times.

  For example, running this on device results in OK:
  SUPPRESS_DEPRECATED_NOTE=yes autopilot3 run 
ubuntu_system_settings.tests.test_about.StorageTestCase.test_disk

  but when I leave out the 'SUPPRESS_DEPRECATED_NOTE=yes', the test
  fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/phablet-tools/+bug/1456350/+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 1418210] Re: Spotify App has changing volume levels per song

[Tim Peeters]

Here is the bug in CuteSpotify:
https://github.com/Elleo/cutespotify/issues/13

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

Title:
  Spotify App has changing volume levels per song

Status in indicator-sound package in Ubuntu:
  Confirmed

Bug description:
  Reported by a user that the per-song levels when using CuteSpotify
  were resetting to really loud, making the application unusable.
  Considering the app has no control over the volume level, this is a
  bug to track down what is happening there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1418210/+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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed

[Tim Peeters]

 timp, the warning goes away if you update the import version to
e.g 1.1, so I guess that's what needs to be changed, but the warning
hint is not helpful in this case


If updating the import version is supposed to fix the warning, we should say 
that in the printed message to help the app developers figure out what's wrong.

** 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/1457528

Title:
  Theme.createStyleComponent deprecation useless warnings are displayed

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

Bug description:
  Take that example

  "import QtQuick 2.0
  import Ubuntu.Components 0.1

  Item {
  Button {
  text: "click"
  }
  }"

  run it on wily, you get those warnings

  "QML Button: Theme.createStyleComponent() is deprecated. Use
  ThemeSettings instead."

  the warning is not helpful, it warns about a standard component issue
  (so something in the responsability of the uitk team, not the code
  writer), lists the issue on something you are not using (what is
  "Theme.createStyleComponent()" that's not used in the code example?),
  it's just confusing...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1418041] Re: dropdown box shows sharp greyed corners

[Tim Peeters]

*** This bug is a duplicate of bug 1357238 ***
https://bugs.launchpad.net/bugs/1357238

** Tags added: ubuntushape

** This bug has been marked a duplicate of bug 1357238
   OptionSelector highlight is not shaped

-- 
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/1418041

Title:
  dropdown box shows sharp greyed corners

Status in the base for Ubuntu mobile products:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Triaged

Bug description:
  In the screen that shows the dropdown to choose a method of payment,
  sharp corners are shown behind the rounded shape. Screenshot attached

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418041/+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 1461729] Re: calling pageStack.pop() in a loop pops too much

[Tim Peeters]

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

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

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

-- 
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/1461729

Title:
  calling pageStack.pop() in a loop pops too much

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

Bug description:
  In Ubuntu.Components 1.1 this was working fine to pop everything from
  a PageStack except the first page:

  while (pageStack.depth > 1) {
pageStack.pop()
  }

  
  In Ubuntu.Components 1.2 this does no longer work, because it pops the first 
page too. My suspicion is that it is related to the animation in the header 
which updates the depth asynchronously.

  See the attached file as a standalone example to reproduce. While it
  works when importing 1.1, it breaks when importing 1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461729/+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 1461729] Re: calling pageStack.pop() in a loop pops too much

[Tim Peeters]

Pop() is called repeatedly before the previous page is actually popped,
because of the animation.

I think we need to disable all animations, or add a pop(bool immediate)
function, or completely make the visuals and pagestack asynchronous,
including copying of the Page in memory to avoid showing a Page (that is
animating out) when it was already popped from the stack and removed
from memory.

-- 
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/1461729

Title:
  calling pageStack.pop() in a loop pops too much

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

Bug description:
  In Ubuntu.Components 1.1 this was working fine to pop everything from
  a PageStack except the first page:

  while (pageStack.depth > 1) {
pageStack.pop()
  }

  
  In Ubuntu.Components 1.2 this does no longer work, because it pops the first 
page too. My suspicion is that it is related to the animation in the header 
which updates the depth asynchronously.

  See the attached file as a standalone example to reproduce. While it
  works when importing 1.1, it breaks when importing 1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461729/+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 1496913] [NEW] RTL switch in UITK component gallery

[Tim Peeters]

Public bug reported:

We should have a switch for RTL in the component gallery. Next to the
theme switch button in the main page header is a good place.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: 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/1496913

Title:
  RTL switch in UITK component gallery

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

Bug description:
  We should have a switch for RTL in the component gallery. Next to the
  theme switch button in the main page header is a good place.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1496913/+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 1500483] [NEW] [sdk] animate header component when app comes back to the foreground

[Tim Peeters]

Public bug reported:

When the header is hidden by scrolling it out of the view in an app, and
the user switches between apps, when an app comes back to the
foreground, the header instantly appears again. This means when going
back to a previous app, the app is not in exactly the same state as
where the user left it.

Example:
- Open gallery-app
- Scroll down to hide the header (you need to have enough photos in the gallery 
to scroll down).
- Long left/right edge swipe to hide send the gallery-app to the background
- Re-open the gallery app

Result:
The gallery-app re-opens with the header visible.


This can be confusing for the user.
Two possible solutions:
1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

After discussing with Olga, we decided to go for solution 1. The header
will show, but it must animate.

** Affects: ubuntu-ux
 Importance: Undecided
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: 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/1500483

Title:
  [sdk] animate header component when app comes back to the foreground

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

Bug description:
  When the header is hidden by scrolling it out of the view in an app,
  and the user switches between apps, when an app comes back to the
  foreground, the header instantly appears again. This means when going
  back to a previous app, the app is not in exactly the same state as
  where the user left it.

  Example:
  - Open gallery-app
  - Scroll down to hide the header (you need to have enough photos in the 
gallery to scroll down).
  - Long left/right edge swipe to hide send the gallery-app to the background
  - Re-open the gallery app

  Result:
  The gallery-app re-opens with the header visible.

  
  This can be confusing for the user.
  Two possible solutions:
  1. Show the header when re-opening the app, but animate it so the user knows 
what is happening
  2. Don't do anything. Header stays hidden and the user can show it as they 
normally would.

  After discussing with Olga, we decided to go for solution 1. The
  header will show, but it must animate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1500483/+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 1466410] Re: Tabs/Pages don't work correctly when Repeater used

[Tim Peeters]

Can you include example code that shows the issue?

-- 
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/1466410

Title:
  Tabs/Pages don't work correctly when Repeater used

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

Bug description:
  Steps to reproduce:

  Follow:
  https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.Tabs/

  Use a Repeater to create two tabs.
  On one of the tabs, press "open page" button.

  Expected: page is opened, and it's possible to go back

  Actual: page is opened, and content is immediately replaced with what
  the tab was showing. once back is pressed, the *page* content is
  shown.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1466410/+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 1467851] Re: Remove warning on deprecated theme for versions < 1.3

[Tim Peeters]

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

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

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

-- 
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/1467851

Title:
  Remove warning on deprecated theme for versions < 1.3

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

Bug description:
  This is slightly related to bug 1457528.

  In my case, I have an application using the 14.10 framework and importing 
Ubuntu.Components 1.0.
  In that version, Theme *is not deprecated*, therefore I shouldn't see any 
warnings.

  That should be the case up to 1.2, where Theme is still documented as
  not being deprecated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1467851/+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 1457528] Re: Theme.createStyleComponent deprecation useless warnings are displayed

[Tim Peeters]

Right, it is a slightly different bug,
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1467851

-- 
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/1457528

Title:
  Theme.createStyleComponent deprecation useless warnings are displayed

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

Bug description:
  Take that example

  "import QtQuick 2.0
  import Ubuntu.Components 0.1

  Item {
  Button {
  text: "click"
  }
  }"

  run it on wily, you get those warnings

  "QML Button: Theme.createStyleComponent() is deprecated. Use
  ThemeSettings instead."

  the warning is not helpful, it warns about a standard component issue
  (so something in the responsability of the uitk team, not the code
  writer), lists the issue on something you are not using (what is
  "Theme.createStyleComponent()" that's not used in the code example?),
  it's just confusing...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1457528/+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 1468760] [NEW] Re-enable header animations

[Tim Peeters]

Public bug reported:

Header animations were disabled because of a bug in this MR
https://code.launchpad.net/~tpeeters/ubuntu-ui-
toolkit/popLoopBug/+merge/261627

They should be enabled again eventually.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: 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/1468760

Title:
  Re-enable header animations

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

Bug description:
  Header animations were disabled because of a bug in this MR
  https://code.launchpad.net/~tpeeters/ubuntu-ui-
  toolkit/popLoopBug/+merge/261627

  They should be enabled again eventually.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1468760/+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 1470136] Re: TextField doc has two text properties

[Tim Peeters]

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

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

-- 
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/1470136

Title:
  TextField doc has two text properties

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

Bug description:
  
https://developer.ubuntu.com/api/apps/qml/sdk-15.04/Ubuntu.Components.TextField/

  The documentation shows two "text" properties.

  One of them is actually inherited by ActionItem and overridden by
  TextField, so the docs shouldn't show the one coming from ActionItem

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1470136/+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 1461729] Re: calling pageStack.pop() in a loop pops too much

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => 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/1461729

Title:
  calling pageStack.pop() in a loop pops too much

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

Bug description:
  In Ubuntu.Components 1.1 this was working fine to pop everything from
  a PageStack except the first page:

  while (pageStack.depth > 1) {
pageStack.pop()
  }

  
  In Ubuntu.Components 1.2 this does no longer work, because it pops the first 
page too. My suspicion is that it is related to the animation in the header 
which updates the depth asynchronously.

  See the attached file as a standalone example to reproduce. While it
  works when importing 1.1, it breaks when importing 1.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1461729/+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 1471848] [NEW] Autopilot always wants to emulate Nexus10 on desktop for UITK gallery tests

[Tim Peeters]

Public bug reported:

I get a lot of failures like this:

Traceback (most recent call last):
  File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 54, in setUp
self.resize_window()
  File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 77, in resize_window
Eventually(Equals((self.app_width, self.app_height
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 423, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: (1280, 
800) != (1280, 776)


because my screen resolution is not high enough to emulate Nexus10. Those 
scenarios should only be executed when the screen resolution is sufficient.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: 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/1471848

Title:
  Autopilot always wants to emulate Nexus10 on desktop for UITK gallery
  tests

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

Bug description:
  I get a lot of failures like this:

  Traceback (most recent call last):
File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 54, in setUp
  self.resize_window()
File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 77, in resize_window
  Eventually(Equals((self.app_width, self.app_height
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 423, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: 
(1280, 800) != (1280, 776)

  
  because my screen resolution is not high enough to emulate Nexus10. Those 
scenarios should only be executed when the screen resolution is sufficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1471848/+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 1471848] Re: Autopilot always wants to emulate Nexus10 on desktop for UITK gallery tests

[Tim Peeters]

For easy reproducability, here I run a single test that fails because of
the screen resolution:

tim@ubuntu:~/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot$ 
autopilot3 run 
ubuntuuitoolkit.tests.gallery.test_gallery.GalleryAppTestCase.test_progress_and_activity
Loading tests from: 
/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot

Tests running...


==
FAIL: 
ubuntuuitoolkit.tests.gallery.test_gallery.GalleryAppTestCase.test_progress_and_activity(Simulating
 Nexus 10 in desktop)
--
Binary content:
  FailedTestScreenshot (image/png)
Empty attachments:
  /var/log/syslog
  process-stdout 
(/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/launcher/launcher)

process-return-code 
(/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/launcher/launcher): 
{{{-15}}}
process-stderr 
(/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/launcher/launcher): 
{{{Testability driver loaded. Wire protocol version is "1.4".}}}
test-log: {{{
17:12:25.465 INFO _launcher:373 - Attempting to launch application 
'/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/launcher/launcher' 
with arguments '-I /home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/modules 
/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml
 
--desktop_file_hint=/home/tim/.local/share/applications/ubuntu-ui-toolkit-gallery.desktop'
 as a normal process
17:12:25.471 INFO _launcher:431 - Launching process: 
['/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/launcher/launcher', 
'-testability', '-I', 
'/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/modules', 
'/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/examples/ubuntu-ui-toolkit-gallery/ubuntu-ui-toolkit-gallery.qml',
 
'--desktop_file_hint=/home/tim/.local/share/applications/ubuntu-ui-toolkit-gallery.desktop']
17:12:37.315 INFO _launcher:544 - waiting for process to exit.
17:12:37.315 INFO _launcher:567 - Killing process 33014
}}}

Traceback (most recent call last):
  File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 54, in setUp
self.resize_window()
  File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 77, in resize_window
Eventually(Equals((self.app_width, self.app_height
  File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 423, in 
assertThat
raise mismatch_error
testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: (1280, 
800) != (1280, 776)

Ran 2 tests in 16.930s
FAILED (failures=1)
tim@ubuntu:~/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot$

-- 
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/1471848

Title:
  Autopilot always wants to emulate Nexus10 on desktop for UITK gallery
  tests

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

Bug description:
  I get a lot of failures like this:

  Traceback (most recent call last):
File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 54, in setUp
  self.resize_window()
File 
"/home/tim/dev/ubuntu-ui-toolkit/m/multiColumnHeader/tests/autopilot/ubuntuuitoolkit/tests/gallery/__init__.py",
 line 77, in resize_window
  Eventually(Equals((self.app_width, self.app_height
File "/usr/lib/python3/dist-packages/testtools/testcase.py", line 423, in 
assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: After 10.0 seconds test failed: 
(1280, 800) != (1280, 776)

  
  because my screen resolution is not high enough to emulate Nexus10. Those 
scenarios should only be executed when the screen resolution is sufficient.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1471848/+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 1472001] Re: Search bar of scopes hides underneath the cached keywords

[Tim Peeters]

*** This bug is a duplicate of bug 1455406 ***
https://bugs.launchpad.net/bugs/1455406

** This bug has been marked a duplicate of bug 1455406
   Search history popover displaced when OSK opens

-- 
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/1472001

Title:
  Search bar of scopes hides underneath the cached keywords

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

Bug description:
  Ubuntu 15.04
  Version : 20150611.3

  Search bar of the scopes hides underneath the Cached keywords
  (automated) drop down Menu.  When you try to give the input through
  the keyboard for the first time, its fine and the Cached keywords are
  drop down at the right place (just Below the search bar). But if you
  click the screen anywhere else and go back to that same search bar,
  the cached keywords pop up and hides the whole search bar

  Test Bed:

  1) Open the Apps Scope.

  2) Click the search bar on the top. Enter a key or two (anything) and you 
should see some cached keywords dropping down the search bar .
  (If not, then try using the phone so that the phone chaches some keywords for 
you)

  3) Then click somewhere (make sure you don't click any app) on the
  screen so that your search bar gets deactivated (Your onscreen
  keyboard will disappear).

  4) Again click the search bar (to reactivate it)

  You will find the effect of the bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1472001/+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 1488922] Re: AdaptivePageLayout fails to show custom header contents

[Tim Peeters]

Something is setting the parent of the contents to null, but I haven't
been able to figure out yet why this happens.

-- 
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/1488922

Title:
  AdaptivePageLayout fails to show custom header contents

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

Bug description:
  In some cases AdaptivePageLayout fails to show the header contents.
  The attached QML example should be showing an orange rectangle in the header 
contents, but it is not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488922/+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 1489591] Re: head sections on the left side of an AdaptivePageLayout 'leak' onto the right side instead of scrolling

[Tim Peeters]

** 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) => 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/1489591

Title:
  head sections on the left side of an AdaptivePageLayout 'leak' onto
  the right side instead of scrolling

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

Bug description:
  When using many head sections on a page in the left side of an
  AdaptivePageLayout they 'leak' into the right side instead of
  scrolling, an example can be found here [0]

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1489591/+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 1488922] Re: AdaptivePageLayout fails to show custom header contents

[Tim Peeters]

The problem was that the PageHeadStyle was some times destroyed

-- 
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/1488922

Title:
  AdaptivePageLayout fails to show custom header contents

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

Bug description:
  In some cases AdaptivePageLayout fails to show the header contents.
  The attached QML example should be showing an orange rectangle in the header 
contents, but it is not.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488922/+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 1489850] Re: Page head sections always start on selectedIndex = 0

[Tim Peeters]

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

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

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

-- 
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/1489850

Title:
  Page head sections always start on selectedIndex = 0

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

Bug description:
  When using page head sections it was expected that assigning
  selectedIndex to a different value would start on that section as in
  this example [0], however what actually happens is that index 0 is
  loaded.

  It should be noted that if you delay the assigning of selectedIndex
  until after everything has been created (with a Timer) it does
  correctly move.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1489850/+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

[Tim Peeters]

Internally the AdaptivePageLayout has an Item with id hiddenPages which
is the parent for the Pages that were added but not visible. We did not
set its anchors, that is why it is null. A quick fix to make its width
not 0 is to make it fill its parent (the AdaptivePageLayout), but then
still the width would change when a Page becomes hidden in a multi-
column layout because the hidden pages would span the full width.

Basically, there is no fixed width that the parent of the hidden pages
must have because the pages may go to different columns when they become
visible.

Is there a way you can prevent the page from re-layouting when it is not
visible?

** 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/1492343

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

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

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 1492343] Re: Pages hidden in an AdpativePageLayout stack have their width changed to zero

[Tim Peeters]

Zsombi what do you mean with "connected badly"?

The page fills its parent, but that is what you want, also when it is
(visible) inside the AdaptivePageLayout. You should not set a fixed
width because the columns can be resized (by changing the window size,
changing the column layouts, or directly changing the column widths by
dragging their edges), and the Pages need to keep filling their column.

Is it not a solution if the Page width becomes 0 when it is invisible
and not to re-layout when changing to 0, as Andrew did above?

-- 
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:
  Confirmed

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 1492343] Re: Pages hidden in an AdpativePageLayout stack have their width changed to zero

[Tim Peeters]

Actually the Page does not fill its parent, but anchors to all sides
except the top, and the Page.height depends on the parent, the header,
and whether the Page has a flickable. As long as we don't move the
header into the page, I don't see a better solution than what we have
now. If we don't anchor it to parent.bottom, then we need to offset its
y depending on the header.

That said, if the header goes into the page, we could set implicitWidth
and implicitHeight of the Page instead of anchoring, or don't set any
anchors/width/height at all (although mostly it will have to fill its
parent).

Anyway, I don't think any choice we make will fix the current bug, so
that's a separate discussion.

-- 
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:
  Confirmed

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 1494387] [NEW] CheckBox needs to track external properties

[Tim Peeters]

Public bug reported:

Often a CheckBox/Switch is used to show the value of a property outside
of the CheckBox. For example:

Switch {
id: hiddenSwitch
checked: !header.exposed
onClicked: header.exposed = !header.exposed
}

At first look, this code may seem fine, but clicking the switch will
trigger checked = !checked, which breaks the binding, so if
header.exposed updates because of events happening outside of the
switch, the switch will be out-of-sync.

Perhaps we need to add some properties to the CheckBox:

CheckBox {
  property Object bindTarget
  property string bindProperty
}

and then the behavior of this:
Switch {
id: exposedSwitch
bindTarget: header
bindProperty: "exposed"
}

can do what we want: the switch shows the value of "exposed", and
clicking the switch should update the "exposed" value (which in turn
will update the state of the switch).

Note that in this case we could not track "!exposed", so if we need
that, some more complicated solution is needed.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Status: 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/1494387

Title:
  CheckBox needs to track external properties

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

Bug description:
  Often a CheckBox/Switch is used to show the value of a property
  outside of the CheckBox. For example:

  Switch {
  id: hiddenSwitch
  checked: !header.exposed
  onClicked: header.exposed = !header.exposed
  }

  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.

  Perhaps we need to add some properties to the CheckBox:

  CheckBox {
property Object bindTarget
property string bindProperty
  }

  and then the behavior of this:
  Switch {
  id: exposedSwitch
  bindTarget: header
  bindProperty: "exposed"
  }

  can do what we want: the switch shows the value of "exposed", and
  clicking the switch should update the "exposed" value (which in turn
  will update the state of the switch).

  Note that in this case we could not track "!exposed", so if we need
  that, some more complicated solution is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1494387/+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 1493178] Re: PageHeadStyle should coordinate Page.head.contents and the ActionBar to not overlap, if possible

[Tim Peeters]

More configurability of the header is coming up in the next month or so.
That will include a way to configure the number of slots in the
ActionBar. I will link this bug to a branch when I start working on it.

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

-- 
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/1493178

Title:
  PageHeadStyle should coordinate Page.head.contents and the ActionBar
  to not overlap, if possible

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

Bug description:
  In my app "Lone Wolf", I use Page.head.contents to add an interactive widget 
to the page header.  It looks like this:
  
https://myapps.developer.ubuntu.com/site_media/appmedia/2015/09/screenshot20150803_125313389.png

  In SDK 1.3, there are up to three action icons shown, instead of the
  one in SDK 1.2.  This means the header is too crowded and
  Page.head.contents may overlap the action icons, depending on how long
  the page title is (and how wide the screen is of course).

  Looking at PageHeadStyle.qml, there is no relationship between
  Page.head.contents.width and ActionBarStyle.width.  But I think there
  should be.

  I don't seem to have any control over ActionBarStyle.numberOfSlots
  myself.  Or any control over how wide the ActionBar is.

  In short, I can't figure out how to replicate my header behavior with
  SDK 1.3.  Maybe the answer is I shouldn't stick widgets in the header?
  But otherwise, I'd consider this a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1493178/+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 1494387] Re: CheckBox needs to track external properties

[Tim Peeters]

Christian, you are right. Overriding the trigger() function works for
me!

However, we do not have this documented, and if I am not an exception
here, many developers may run into this issue, so I keep the bug open,
but I will update its description to say that we need documentation.

** Description changed:

  Often a CheckBox/Switch is used to show the value of a property outside
  of the CheckBox. For example:
  
  Switch {
- id: hiddenSwitch
- checked: !header.exposed
- onClicked: header.exposed = !header.exposed
+ id: hiddenSwitch
+ checked: !header.exposed
+ onClicked: header.exposed = !header.exposed
  }
  
  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.
  
- Perhaps we need to add some properties to the CheckBox:
- 
- CheckBox {
-   property Object bindTarget
-   property string bindProperty
+ --- update 2015-09-11 (thanks Christian) ---
+ It appears to work like this:
+ Switch {
+ id: hiddenSwitch
+ checked: header.exposed
+ function trigger() { header.exposed = !header.exposed; }
  }
  
- and then the behavior of this:
- Switch {
- id: exposedSwitch
- bindTarget: header
- bindProperty: "exposed"
- }
- 
- can do what we want: the switch shows the value of "exposed", and
- clicking the switch should update the "exposed" value (which in turn
- will update the state of the switch).
- 
- Note that in this case we could not track "!exposed", so if we need
- that, some more complicated solution is needed.
+ so DON'T use the onClicked or onTriggered signal as you would expect,
+ but override the trigger() function. We need to document this.

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

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

-- 
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/1494387

Title:
  CheckBox needs to track external properties

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

Bug description:
  Often a CheckBox/Switch is used to show the value of a property
  outside of the CheckBox. For example:

  Switch {
  id: hiddenSwitch
  checked: !header.exposed
  onClicked: header.exposed = !header.exposed
  }

  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.

  --- update 2015-09-11 (thanks Christian) ---
  It appears to work like this:
  Switch {
  id: hiddenSwitch
  checked: header.exposed
  function trigger() { header.exposed = !header.exposed; }
  }

  so DON'T use the onClicked or onTriggered signal as you would expect,
  but override the trigger() function. We need to document this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1494387/+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 1495408] Re: Black square in header

[Tim Peeters]

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

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

** Changed in: canonical-devices-system-image
 Assignee: Zoltan Balogh (bzoltan) => 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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495422] [NEW] CMake warnings: Policy CMP0028 is not set

[Tim Peeters]

Public bug reported:

I get a bunch of CMake warnings when I try to compile gallery-app:


tim@ubuntu:~/dev/r/gallery-app$ cmake .
-- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE) 
-- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE) 
-- Autopilot tests enabled.
-- Configuring done
CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "gallery-app" links to target "Qt5::Xml" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "gallery-medialoader" links to target "Qt5::Widgets" but the target
  was not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 
(add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "command-line-parser" links to target "Qt5::Widgets" but the target
  was not found.  Perhaps a find_package() call is missing for an IMPORTED
  target, or an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 
(add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "resource" links to target "Qt5::Widgets" but the target was not
  found.  Perhaps a find_package() call is missing for an IMPORTED target, or
  an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 (add_executable):
  Policy CMP0028 is not set: Double colon in target name means ALIAS or
  IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
  Use the cmake_policy command to set the policy and suppress this warning.

  Target "video" links to target "Qt5::Xml" but the target was not found.
  Perhaps a find_package() call is missing for an IMPORTED target, or an
  ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.

-- Generating done
-- Build files have been written to: /home/tim/dev/r/gallery-app
tim@ubuntu:~/dev/r/gallery-app$

** Affects: gallery-app (Ubuntu)
 Importance: Undecided
 Status: New

[Touch-packages] [Bug 1495408] Re: Black square in header

[Tim Peeters]

I reproduced the bug as described above on device, but I can also
reproduce it on my laptop with gallery-app (click on a photo, and then
go back).

-- 
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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] Re: Black square in header

[Tim Peeters]

I reproduced the bug (with gallery-app on desktop) with UITK staging
r1612, and verified that the bug is not present in r1611, so it broke
with this MR: https://code.launchpad.net/~zsombi/ubuntu-ui-
toolkit/cppActionItem/+merge/268348

-- 
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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495422] Re: CMake warnings: Policy CMP0028 is not set

[Tim Peeters]

I reproduced the bug with UITK staging r1612, and verified that the bug
is not present in r1611, so it broke with this MR:
https://code.launchpad.net/~zsombi/ubuntu-ui-
toolkit/cppActionItem/+merge/268348

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

Title:
  CMake warnings:  Policy CMP0028 is not set

Status in gallery-app package in Ubuntu:
  New

Bug description:
  I get a bunch of CMake warnings when I try to compile gallery-app:

  
  tim@ubuntu:~/dev/r/gallery-app$ cmake .
  -- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE) 
  -- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE) 
  -- Autopilot tests enabled.
  -- Configuring done
  CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "gallery-app" links to target "Qt5::Xml" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "gallery-medialoader" links to target "Qt5::Widgets" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "command-line-parser" links to target "Qt5::Widgets" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "resource" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 
(add_executable):
Policy CMP0028 is not set: Double colon in targ

[Touch-packages] [Bug 1495422] Re: CMake warnings: Policy CMP0028 is not set

[Tim Peeters]

sorry, I commented on the wrong bug! Ignore the comment above!

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

Title:
  CMake warnings:  Policy CMP0028 is not set

Status in gallery-app package in Ubuntu:
  New

Bug description:
  I get a bunch of CMake warnings when I try to compile gallery-app:

  
  tim@ubuntu:~/dev/r/gallery-app$ cmake .
  -- Could NOT find Lcov (missing:  LCOV_EXECUTABLE GENHTML_EXECUTABLE) 
  -- Could NOT find gcovr (missing:  GCOVR_EXECUTABLE) 
  -- Autopilot tests enabled.
  -- Configuring done
  CMake Warning (dev) at src/CMakeLists.txt:51 (add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "gallery-app" links to target "Qt5::Xml" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at src/medialoader/CMakeLists.txt:27 (add_library):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "gallery-medialoader" links to target "Qt5::Widgets" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/command-line-parser/CMakeLists.txt:12 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "command-line-parser" links to target "Qt5::Widgets" but the target
was not found.  Perhaps a find_package() call is missing for an IMPORTED
target, or an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/mediamonitor/CMakeLists.txt:18 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "mediamonitor" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/resource/CMakeLists.txt:12 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.

Target "resource" links to target "Qt5::Widgets" but the target was not
found.  Perhaps a find_package() call is missing for an IMPORTED target, or
an ALIAS target is missing?
  This warning is for project developers.  Use -Wno-dev to suppress it.

  CMake Warning (dev) at tests/unittests/video/CMakeLists.txt:28 
(add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the

[Touch-packages] [Bug 1495408] Re: Black square in header

[Tim Peeters]

Bug can be reproduced by running the qml code below, clicking the 'next'
button, and then clicking the back button in the header:

import QtQuick 2.4
import Ubuntu.Components 1.2

MainView {
width: units.gu(40)
height: units.gu(60)
Component.onCompleted: pageStack.push(page1)

PageStack {
id: pageStack
}

Page {
id: page1
title: "one"
Button {
anchors.centerIn: parent
text: "next"
onClicked: pageStack.push(page2)
}
}
Page {
id: page2
title: "two"
visible: false

head.backAction: Action {
iconName: "back"
onTriggered: pageStack.pop()
}
}
}

-- 
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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495408] Re: Black square in header

[Tim Peeters]

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

** Changed in: canonical-devices-system-image
 Assignee: Tim Peeters (tpeeters) => (unassigned)

-- 
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/1495408

Title:
  Black square in header

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

Bug description:
  current build number: 122
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en

  Same on latest arale

  There is a black square in the header in several applications
  (address-book, messaging, dialler, cf screenshots)

  To display the black square:
  - dialler: open 'Recent calls'
  - messaging: tap on a message and go back
  - contact: tap on a contact

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1495408/+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 1495451] Re: Page pushed on a stack gets instantiated twice, and PageStack.push() returns null

[Tim Peeters]

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

** 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/1495451

Title:
  Page pushed on a stack gets instantiated twice, and PageStack.push()
  returns null

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

Bug description:
  It looks to me like a regression introduced by the latest UITK landing 
(1.3.1627+15.04.20150908-0ubuntu1).
  See the attached standalone reproducer (run it with qmlscene).
  In a MainView, pushing a page component on a page stack instantiates the page 
twice.
  Additionally, the result of pageStack.push(pageComponent) is null, and it 
seems the 'currentPage' property of the stack is not updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1495451/+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 1494387] Re: CheckBox needs to track external properties

[Tim Peeters]

** Description changed:

  Often a CheckBox/Switch is used to show the value of a property outside
  of the CheckBox. For example:
  
  Switch {
  id: hiddenSwitch
  checked: !header.exposed
  onClicked: header.exposed = !header.exposed
  }
  
  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.
  
+ Perhaps we need to add some properties to the CheckBox:
+ 
+ CheckBox {
+   property Object bindTarget
+   property string bindProperty
+ }
+ 
+ and then the behavior of this:
+ Switch {
+ id: exposedSwitch
+ bindTarget: header
+ bindProperty: "exposed"
+ }
+ 
+ can do what we want: the switch shows the value of "exposed", and
+ clicking the switch should update the "exposed" value (which in turn
+ will update the state of the switch).
+ 
+ Note that in this case we could not track "!exposed", so if we need
+ that, some more complicated solution is needed.
+ 
  --- update 2015-09-11 (thanks Christian) ---
  It appears to work like this:
  Switch {
- id: hiddenSwitch
- checked: header.exposed
- function trigger() { header.exposed = !header.exposed; }
+ id: hiddenSwitch
+ checked: header.exposed
+ function trigger() { header.exposed = !header.exposed; }
  }
  
  so DON'T use the onClicked or onTriggered signal as you would expect,
  but override the trigger() function. We need to document this.

-- 
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/1494387

Title:
  CheckBox needs to track external properties

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

Bug description:
  Often a CheckBox/Switch is used to show the value of a property
  outside of the CheckBox. For example:

  Switch {
  id: hiddenSwitch
  checked: !header.exposed
  onClicked: header.exposed = !header.exposed
  }

  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.

  Perhaps we need to add some properties to the CheckBox:

  CheckBox {
property Object bindTarget
property string bindProperty
  }

  and then the behavior of this:
  Switch {
  id: exposedSwitch
  bindTarget: header
  bindProperty: "exposed"
  }

  can do what we want: the switch shows the value of "exposed", and
  clicking the switch should update the "exposed" value (which in turn
  will update the state of the switch).

  Note that in this case we could not track "!exposed", so if we need
  that, some more complicated solution is needed.

  --- update 2015-09-11 (thanks Christian) ---
  It appears to work like this:
  Switch {
  id: hiddenSwitch
  checked: header.exposed
  function trigger() { header.exposed = !header.exposed; }
  }

  so DON'T use the onClicked or onTriggered signal as you would expect,
  but override the trigger() function. We need to document this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1494387/+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 1494387] Re: CheckBox needs to track external properties

[Tim Peeters]

More people run into problems here: http://pastebin.ubuntu.com/12417204/

-- 
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/1494387

Title:
  CheckBox needs to track external properties

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

Bug description:
  Often a CheckBox/Switch is used to show the value of a property
  outside of the CheckBox. For example:

  Switch {
  id: hiddenSwitch
  checked: !header.exposed
  onClicked: header.exposed = !header.exposed
  }

  At first look, this code may seem fine, but clicking the switch will
  trigger checked = !checked, which breaks the binding, so if
  header.exposed updates because of events happening outside of the
  switch, the switch will be out-of-sync.

  Perhaps we need to add some properties to the CheckBox:

  CheckBox {
property Object bindTarget
property string bindProperty
  }

  and then the behavior of this:
  Switch {
  id: exposedSwitch
  bindTarget: header
  bindProperty: "exposed"
  }

  can do what we want: the switch shows the value of "exposed", and
  clicking the switch should update the "exposed" value (which in turn
  will update the state of the switch).

  Note that in this case we could not track "!exposed", so if we need
  that, some more complicated solution is needed.

  --- update 2015-09-11 (thanks Christian) ---
  It appears to work like this:
  Switch {
  id: hiddenSwitch
  checked: header.exposed
  function trigger() { header.exposed = !header.exposed; }
  }

  so DON'T use the onClicked or onTriggered signal as you would expect,
  but override the trigger() function. We need to document this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1494387/+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 1257307] Re: [sdk] The pagestacks should allow to pop more than one page at the time

[Tim Peeters]

PageStack will be deprecated in favor of AdaptivePageLayout.
AdaptivePageLayout already has a removePages() function that takes a
parameter which determines which pages are removed from the stack.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Incomplete => 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/1257307

Title:
  [sdk] The pagestacks should allow to pop more than one page at the
  time

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

Bug description:
  In some cases you have several level of pages stacked, it would be
  useful to let be able to pop more than once a the time

  e.g you have a start page, push a list, push a confirmation/option
  dialog, then you want to go back to the start screen ... right now you
  have to pop one level and then have some logic to pop down another
  level when getting there.

  It would be nice to be able to pop(n), maybe with 0=bottom of the
  stack

  ---UX comment-

  The solution as per comment #3 seems plausible. I do agree with
  comment #4 + #4. A sudden change in the general logic and page stack
  navigation is going to cause confusion to the user. The described use
  case (example?) seems to be an edge case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1257307/+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 1247865] Re: Pages Stack misses animations

[Tim Peeters]

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

-- 
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/1247865

Title:
  Pages Stack misses animations

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

Bug description:
  In the Qt Documentation it says:
  "PageStack automatically provides appropriate transition animations as the 
user moves from one page to another. The type of animation that occurs is fixed 
according to the user interface guidelines for the platform and cannot be 
customised."
  http://doc.qt.digia.com/qt-components-symbian-1.0/qml-pagestack.html

  However, on Ubuntu (Touch) there is no animation at all. :(

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1247865/+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 1369939] Re: Default value for MainView.useDeprecatedToolbar will change to false in 1.2

[Tim Peeters]

** 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/1369939

Title:
  Default value for MainView.useDeprecatedToolbar will change to false
  in 1.2

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

Bug description:
  This was announced on the mailing lists

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1369939/+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 1396190] Re: Inactive pages bleed through other pages

[Tim Peeters]

This is no longer an issue with AdaptivePageLayout, which is now
recommended instead of PageStack.

** 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/1396190

Title:
  Inactive pages bleed through other pages

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

Bug description:
  Got a page stack.

  Got pages.

  See parts of inactive pages show up in front of the active one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1396190/+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 1214442] Re: [sdk]Add toolbar component

[Tim Peeters]

Femma can you elaborate on why it cannot be fixed as a bug?

Note that I don't have access to the kanban board that you linked.

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Triaged => 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/1214442

Title:
  [sdk]Add toolbar component

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

Bug description:
  I've written a Sidebar component for use in a adaptive layouts.

  The code is available at https://github.com/iBeliever/ubuntu-ui-
  extras/blob/master/Sidebar.qml.

  It provides a nice animation on sliding in/out, and also has a good
  default color that looks good on top of Suru themes.

  A lot of other apps have started to use it. Would it be possible to
  get this or a similar component included in the UI toolkit?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1214442/+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 1640135] Re: Missing dependency of examples on qml-module-qtqml-models2

[Tim Peeters]

** 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/1640135

Title:
  Missing dependency of examples on qml-module-qtqml-models2

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

Bug description:
  The first version of the uitk-gallery snap shows me this when opening
  the colors page:

  
  ui-toolkit/examples/ubuntu-ui-toolkit-gallery/Colors.qml:19:1: module 
"QtQml.Models" is not installed
  import QtQml.Models 2.1
  ^)

  Adding the qml-module-qtqml-models2 dependency for ubuntu-ui-toolkit-
  examples will fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1640135/+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 1558018] Re: Scrolling of icons in Toolbar

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit (Ubuntu)
   Status: Confirmed => 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/1558018

Title:
  Scrolling of icons in Toolbar

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

Bug description:
  Currently, when the icons do not all fit in the toolbar, an overflow
  button is shown that shows an overflow popover/panel when clicked.
  This needs to be replaced by icon scrolling instead.

  See https://docs.google.com/document/d/1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q/edit

  UX solution:
  
https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.w16v0yn510iy
 is this not what you need?

  https://docs.google.com/document/edit?hgd=1&id=1F-zD6CF8YFfA-
  nAtpdRniCqwUNJhSDJVFrRO76A1M-Q#heading=h.duaef4xy7sqv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1558018/+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 1659869] Re: Page header and focus behaviour

[Tim Peeters]

I agree about the focus order within a page (not sure which page should
have focus first though). But I think this will be valid for all apps,
so we don't need to make it configurable, just fix the current focus
order.

Can we get feedback from design on this?

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

** Also affects: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

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

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

-- 
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/1659869

Title:
  Page header and focus behaviour

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

Bug description:
  We have been discussing on IRC about the focus path on page header->
  page-contents.

  Some apps require a fine tuning on the focus path for the header
  buttons and contents. This is not possible today since we do not have
  access to all header objects (only actions).

  Another problem is that the page first receive focus on your contents
  and after the header. This can be annoying if the focus starts on the
  header because the focus go to another page before enter on page
  contents (check img0.png). would be nice to allow apps to choose which
  is the desired focus paths between pages and headers. (something like
  img1.png)

  And in the end would be nice to have a AdaptativePageLayout method to
  allow user to access a page pages on index or something else in case
  of the user want to move focus to a different page in the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1659869/+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 1662220] Re: [ListItem] Popupmenu shows traces of disabled actions

[Tim Peeters]

Can it be reproduced with ActionSelectionPopover too? That is the base
component of the ListItemPopover.

-- 
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/1662220

Title:
  [ListItem] Popupmenu shows traces of disabled actions

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

Bug description:
  Invisible actions on ListItem appears on top of the popup menu (check
  image)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1662220/+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 1662847] [NEW] UITK examples source in a separate (not UITK) project

[Tim Peeters]

Public bug reported:

Put the UITK examples in a separate project that also includes the
snapcraft.yaml file.

Currently, ubuntu-ui-toolkit-examples includes only the snap
configuration, but it pulls in the deb files from the overlay PPA to
build the snap file.

So the sources can be moved from the ubuntu-ui-toolkit to the ubuntu-ui-
toolkit-examples project on launchpad.

** Affects: ubuntu-ui-toolkit-examples
 Importance: Undecided
 Assignee: Tim Peeters (tpeeters)
 Status: New

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: Undecided
 Assignee: Tim Peeters (tpeeters)
 Status: New

** Also affects: ubuntu-ui-toolkit (Ubuntu)
   Importance: Undecided
   Status: New

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

** 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/1662847

Title:
  UITK examples source in a separate (not UITK) project

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

Bug description:
  Put the UITK examples in a separate project that also includes the
  snapcraft.yaml file.

  Currently, ubuntu-ui-toolkit-examples includes only the snap
  configuration, but it pulls in the deb files from the overlay PPA to
  build the snap file.

  So the sources can be moved from the ubuntu-ui-toolkit to the ubuntu-
  ui-toolkit-examples project on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1662847/+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 1576282] Re: Snaps built from deb can't be gettext translated

[Tim Peeters]

** Changed in: ubuntu-app-platform
 Assignee: Tim Peeters (tpeeters) => Christian Dywan (kalikiana)

-- 
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/1576282

Title:
  Snaps built from deb can't be gettext translated

Status in Canonical System Image:
  In Progress
Status in Snapcraft:
  New
Status in Ubuntu App Platform:
  In Progress
Status in snapcraft package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Currently it seems not possible to have working gettext translations
  without included a patch glibc build in your snap

  - the core image doesn't have locales definition

  that can be worked around by including locales definitions in the
  snap, though that's tedious, ideally snapcraft would help there

  
  - traditional desktop applications are built with calls to 'bindtextdomain 
("domain", LOCALEDIR)', where LOCALDIR is defined at buildtime and so pointing 
to /usr 

  there seems to be no way to redirect to another directory at runtime

  
  - desktop applications needs system library translations sometime which means 
langpacks need to be included in snaps

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1576282/+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 1640135] Re: Missing dependency of examples on qml-module-qtqml-models2

[Tim Peeters]

** Changed in: ubuntu-ui-toolkit-examples
   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/1640135

Title:
  Missing dependency of examples on qml-module-qtqml-models2

Status in ubuntu-ui-toolkit-examples:
  In Progress
Status in ubuntu-ui-toolkit package in Ubuntu:
  Fix Released

Bug description:
  The first version of the uitk-gallery snap shows me this when opening
  the colors page:

  
  ui-toolkit/examples/ubuntu-ui-toolkit-gallery/Colors.qml:19:1: module 
"QtQml.Models" is not installed
  import QtQml.Models 2.1
  ^)

  Adding the qml-module-qtqml-models2 dependency for ubuntu-ui-toolkit-
  examples will fix it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1640135/+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 1662847] Re: UITK examples source in a separate (not UITK) project

[Tim Peeters]

** Description changed:

  Put the UITK examples in a separate project that also includes the
  snapcraft.yaml file.
  
  Currently, ubuntu-ui-toolkit-examples includes only the snap
  configuration, but it pulls in the deb files from the overlay PPA to
  build the snap file.
  
- So the sources can be moved from the ubuntu-ui-toolkit to the ubuntu-ui-
- toolkit-examples project on launchpad.
+ So the examples sources can be moved from the ubuntu-ui-toolkit to the
+ ubuntu-ui-toolkit-examples project on launchpad.

-- 
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/1662847

Title:
  UITK examples source in a separate (not UITK) project

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

Bug description:
  Put the UITK examples in a separate project that also includes the
  snapcraft.yaml file.

  Currently, ubuntu-ui-toolkit-examples includes only the snap
  configuration, but it pulls in the deb files from the overlay PPA to
  build the snap file.

  So the examples sources can be moved from the ubuntu-ui-toolkit to the
  ubuntu-ui-toolkit-examples project on launchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ui-toolkit-examples/+bug/1662847/+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 1424588] Re: unable to center popover in caller

[Tim Peeters]

Currently a popover without a caller is added to the top of the screen
in order to leave space at the bottom to make it easy for the user to
tap that area in order to close the popover. I assume we want to be
consistent between the apps (including browser). Should we change the
default behavior in the UITK to center the popover vertically, or should
the design for the popover in the webbrowser be updated?

-- 
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/1424588

Title:
  unable to center popover in caller

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

Bug description:
  The design for the browser app’s contextual menu requires the popover
  to be centered inside its caller (the webview). See
  
https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g34608d763_079
  for reference. The popover is opened using PopupUtils.open(…).

  I’ve tried two different approaches to achieve that, but none actually
  works:

   - passing the webview as the caller
   - passing no caller parameter at all

  In both cases, the popover is horizontally centered, but it’s anchored
  to the top of the scene.

  I’m attaching a standalone example that demonstrates the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1424588/+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 1420748] Re: Always reserve space for three actions in header

[Tim Peeters]

** Tags added: design-sync

-- 
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/1420748

Title:
  Always reserve space for three actions in header

Status in Ubuntu UX bugs:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  Confirmed

Bug description:
  Currently there is room for 3 actions directly in the header,
  including a back/cancel button or tabs button on the left side.

  So without a button on the left, there is room for 3 actions on the
  right, but when there is an action on the left, only 2 actions are
  allowed on the right side. I think this is confusing for the users
  (some times you have 3 buttons, and some times 1 normal button plus an
  overflow button with two actions in the overflow) and not really
  necessary.

  I propose to (on a phone) always reserve space for 3 actions on the
  right side in the header, even if there is an action in the left of
  the header.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1420748/+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 1424592] [NEW] Header needs locked and visible properties

[Tim Peeters]

Public bug reported:

The header API proposal 
https://docs.google.com/a/canonical.com/document/d/1wUUKtPmRmwbUELC1BUB9l0VOAwS_zAPRSCqMopUxR1c/edit#heading=h.yv1xue68vkeu
 adds Page.head.locked and Page.head.visible properties that the developer can 
use to lock and show/hide the header. Several developers asked how to hide/show 
the header. Currently the header can be hidden by setting the title to "", but 
that causes problems, see 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1402054
Current locking of the header is done by setting Page.flickable = null, which 
is not very intuitive API.

We need to implement the proper way of locking/showing/hiding the header
by adding head.locked and head.visible properties.

** Affects: ubuntu-ui-toolkit (Ubuntu)
 Importance: High
 Assignee: Tim Peeters (tpeeters)
 Status: Confirmed


** Tags: header

** Tags added: header

-- 
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/1424592

Title:
  Header needs locked and visible properties

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

Bug description:
  The header API proposal 
https://docs.google.com/a/canonical.com/document/d/1wUUKtPmRmwbUELC1BUB9l0VOAwS_zAPRSCqMopUxR1c/edit#heading=h.yv1xue68vkeu
 adds Page.head.locked and Page.head.visible properties that the developer can 
use to lock and show/hide the header. Several developers asked how to hide/show 
the header. Currently the header can be hidden by setting the title to "", but 
that causes problems, see 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1402054
  Current locking of the header is done by setting Page.flickable = null, which 
is not very intuitive API.

  We need to implement the proper way of locking/showing/hiding the
  header by adding head.locked and head.visible properties.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424592/+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 1424592] Re: Header needs locked and visible properties

[Tim Peeters]

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

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

-- 
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/1424592

Title:
  Header needs locked and visible properties

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

Bug description:
  The header API proposal 
https://docs.google.com/a/canonical.com/document/d/1wUUKtPmRmwbUELC1BUB9l0VOAwS_zAPRSCqMopUxR1c/edit#heading=h.yv1xue68vkeu
 adds Page.head.locked and Page.head.visible properties that the developer can 
use to lock and show/hide the header. Several developers asked how to hide/show 
the header. Currently the header can be hidden by setting the title to "", but 
that causes problems, see 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1402054
  Current locking of the header is done by setting Page.flickable = null, which 
is not very intuitive API.

  We need to implement the proper way of locking/showing/hiding the
  header by adding head.locked and head.visible properties.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424592/+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 1424592] Re: Header needs locked and visible properties

[Tim Peeters]

** 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/1424592

Title:
  Header needs locked and visible properties

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

Bug description:
  The header API proposal 
https://docs.google.com/a/canonical.com/document/d/1wUUKtPmRmwbUELC1BUB9l0VOAwS_zAPRSCqMopUxR1c/edit#heading=h.yv1xue68vkeu
 adds Page.head.locked and Page.head.visible properties that the developer can 
use to lock and show/hide the header. Several developers asked how to hide/show 
the header. Currently the header can be hidden by setting the title to "", but 
that causes problems, see 
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1402054
  Current locking of the header is done by setting Page.flickable = null, which 
is not very intuitive API.

  We need to implement the proper way of locking/showing/hiding the
  header by adding head.locked and head.visible properties.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424592/+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 1424635] Re: Locked header does not work with conditional loading components

[Tim Peeters]

I added some prints in our Page code. In Page10.qml (also valid for Page
1.1), I have this now:

// avoid using parent.height because parent may be a Loader which does not 
have its height set.
height: parentNode ? page.flickable ? parentNode.height : parentNode.height 
- internal.headerHeight : undefined
onHeightChanged: print("height of "+page+" changed to "+parentNode.height+" 
- "+internal.headerHeight+" = "+height)

and this is being printed for the incorrect page:

qml: parent node of Page11_QMLTYPE_35(0x2779620) = Tab_QMLTYPE_26(0x217f4f0)
qml: parent height = 400
qml: height of Page11_QMLTYPE_35(0x2779620) changed to 400 - 72 = 328
qml: parent node of Page11_QMLTYPE_35(0x2779620) = Tab_QMLTYPE_26(0x217f4f0)
qml: parent height = 400
qml: height of Page11_QMLTYPE_35(0x2779620) changed to 400 - 72 = 400

so it seems that height is not updated, even though
internal.headerHeight is correct here.

-- 
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/1424635

Title:
  Locked header does not work with conditional loading components

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

Bug description:
  Trying to use the flickable property to make the header locked does
  not work as expected with conditional loading components. The attached
  sample QML code shows the issue. On the first tab, where the component
  is directly loaded, the header is locked and working as expected. On
  the second one the flickable component seems to be drawn over the
  header. The problem seems to be gone if we change the window height.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424635/+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 1424635] Re: Locked header does not work with conditional loading components

[Tim Peeters]

It is a problem here that the Loader has anchors, and thus width and
height, and will set the width and height of its loaded item
accordingly, overriding the logic we have in the Page.

-- 
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/1424635

Title:
  Locked header does not work with conditional loading components

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

Bug description:
  Trying to use the flickable property to make the header locked does
  not work as expected with conditional loading components. The attached
  sample QML code shows the issue. On the first tab, where the component
  is directly loaded, the header is locked and working as expected. On
  the second one the flickable component seems to be drawn over the
  header. The problem seems to be gone if we change the window height.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424635/+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 1424635] Re: Locked header does not work with conditional loading components

[Tim Peeters]

I modified the example code like this: http://paste.ubuntu.com/10372933/
and now it works fine. It is not really a bug in UITK, but a result of
how the UITK works and how the Loader changes the size of its children,
see Loader sizing behavior on http://doc-snapshot.qt-project.org/qt5-5.4
/qml-qtquick-loader.html

-- 
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/1424635

Title:
  Locked header does not work with conditional loading components

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

Bug description:
  Trying to use the flickable property to make the header locked does
  not work as expected with conditional loading components. The attached
  sample QML code shows the issue. On the first tab, where the component
  is directly loaded, the header is locked and working as expected. On
  the second one the flickable component seems to be drawn over the
  header. The problem seems to be gone if we change the window height.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1424635/+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