This is solved with the new PageHeader (see
https://developer.ubuntu.com/en/blog/2016/02/24/pageheader-tutorial/ for
an introduction). If you don't want the topMargin in the ListView,
simply don't set the PageHeader.flickable property.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to ubuntu-ui-toolkit in Ubuntu.
https://bugs.launchpad.net/bugs/1358423
Title:
topMargin can become wrong on page structure changes
Status in ubuntu-ui-toolkit package in Ubuntu:
Fix Released
Bug description:
That created bug #1356292 in ubuntu-system-settings
Copying a potential explanation of the issue (from IRC discussions)
"I guess what happens is that the Page detects the listview being top-
anchored but then fails to detect that changes during runtime and
keeps on setting topMargin on the ListView
a flickable is auto-detected and assigned to Page.flickable, of which
the margins are updated by the header
if you set Page.flickable to null, you'll have a fixed header and all
contents below it
"
I'm attaching a small example, that's using a page with a non visible button
and a listview, once the list is loaded the button is made visible, which leads
to have the list incorrectly placed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1358423/+subscriptions
--
Mailing list: https://launchpad.net/~ubuntu-sdk-bugs
Post to : ubuntu-sdk-bugs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-sdk-bugs
More help : https://help.launchpad.net/ListHelp
