| 2015-09-02 13:00:45 |
Didier Roche-Tolomelli |
description |
If you don't reload a PageWithBottomEdge, 2 positionning issues happens on bottom restore (so at the second reveal restore).
reloadBottomEdgePage: false.
There are 2 differents kinds of bugs, after the second reveal:
1. If you PageWithBottomEdge doesn't contain any flickable, then, there is an height offset (the height of your page is reduced by the header size, clipping some parts not visible at the end of the page)
2. If you PageWithBottomEdge contains a flickable, then the bottomEdgePage is going over the header bar.
Some workaround can be on the stackpage for both case:
StackPage {
onCurrentPageChanged: {
if (currentPage === <mainpage>.bottomEdgePage) {
<mainpage>.bottomEdgePage.y = <mainpage>.header.height
<mainpage>.bottomEdgePage.activate();
}
}
-> This restores the height.
Tested with Ubuntu Components 1.2 |
If you don't reload a PageWithBottomEdge, 2 positionning issues happens on bottom restore (so at the second reveal restore).
reloadBottomEdgePage: false.
There are 2 differents kinds of bugs, after the second reveal:
1. If you PageWithBottomEdge doesn't contain any flickable, then, there is an height offset (the height of your page is reduced by the header size, clipping some parts not visible at the end of the page)
2. If you PageWithBottomEdge contains a flickable, then the bottomEdgePage is going over the header bar.
Some workaround can be on the stackpage for both case:
StackPage {
onCurrentPageChanged: {
if (currentPage === <mainpage>.bottomEdgePage) {
<mainpage>.bottomEdgePage.y = <mainpage>.header.height
<mainpage>.bottomEdgePage.activate();
}
}
-> This restores the height.
Tested with Ubuntu Components 1.2.
Please find attach an example to trigger the issue |
|
