Cascades Development

[gyubok]

Since a lot of people are able to reproduce this behavior, I guess it is a bug. I think this bug is pretty serious because RIM is expecting BlackBerry 10 users to constantly go in an out of apps, if the user comes back to the app and find the animation broken, it will seriously take away the BlackBerry 10 flow experience.

I have never logged a bug report, or even know how to. Can someone either do it or teach me? It would be fastest if someone from RIM see this thread.

[peter9477]

I created https://www.blackberry.com/jira/browse/BBTEN-692 to cover this.

We've also asked for someone from the native dev group to join in here with some sort of response, since as noted above it's a pretty serious problem.

[robbieDubya]

Thanks. I'm going to try and build a test case to reproduce and escalate.

[robbieDubya]

Reproduced: on Dev Alpha A running 10.0.09.2320

import bb.cascades 1.0

Page {
    Container {
        layout: StackLayout {
        }
        Container {
            layout: AbsoluteLayout {
            }
            preferredHeight: 500
            Label {
                id: fred
                text: "Fred"
            }
        }
        Button {
            text: "Dance Freddy DANCE!"
            onClicked: {
                fred.translationY = 400 - fred.translationY;
            }
        }
    }
}

[hendrik]

We are also experiencing this bug in our app since the latest SDK update. The transition animations are broken after the app has been minimized once. Only a restart of the app fixes the problem.

I discovered that the bug does NOT occur if "Application.cover" is set like e.g. in the QML Cookbook sample app.

However we have not yet decided whether we prefer to display an app cover or just the default thumbnail view when our app is minimized, so it would be appreciated if this bug could be fixed before the final release of the OS.

[robbieDubya · Accepted solution]

Good news, this appears fixed on newer (internal) builds. Tested on 2372.

[peter9477]

Great news, robbieDubya.

For my purposes and probably most of us, that's probably enough. We just need to test animation-related stuff without thumbnailing the app, and if we thumbnail the app we ignore our animations for now.

[jasoncheung]

That is good news.

For our current releases, should we wait for the upcoming SDK build or shall we do the workaround for now?

[codealot]

Great!! now I can get back to coding in calm . Thanks for the info.

[peter9477]

Jason, I'd suggest leave your code as-is, since it will clearly be fixed for launch. Personally, I'm not changing a thing, for now, anyway....