PageStack::push() should return the object that was pushed

right now I'm working around this by havving a function object property in the page:

FooPage.qml:
...
    /// work around LP(#1361919)
    property var activateCb;
....
            onClicked: activateCb("Foo")
....

Bar.qml:
            pageStack.push(Qt.resolvedUrl("FooPage.qml"),
                           {
                               activateCb: myActivateFunction
                           });
....

could you use PageStack.currentPage instead?

I can add a returned page to push(), but note that push returns immediately, and header animations (to be enabled soon) may still be running when push() returns, and the new page will not be active (and on top of the stack yet) while the header is still animating. Can this give problems in your application?

So how it will work when header animations are enabled:

- Push(yourpage) is called // yourpage may be a Page, Component, or qml file
- Fade out of the old header started
- Push *RETURNS* immediately (before fade out animation is finished)
- Fade out of old header finishes
- New page object is created (if needed), and pushed on the stack
- Fade in of new header

I plan to make Push return the newly created page as follow:

- Push(yourpage) is called
- New page object created (if needed)
- Fade out animation started
- Push() *RETURNS* new page object
- Fade out animation finishes
- New page object pushed on stack
- Fade in animation of new header

So note that when Push() returns the value, the new page object exists, but it may not be active (Page.active is not true) yet, and it is not yet on top of the stack. This is only guaranteed after the header animations finish.

Why is this bug critical? Which critical change do you need to make in which app?

Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown