Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
08-29-2014 09:34 AM
There seems to be a rendering issue in Cascades when multiple navigation animations are running at the same time (e.g. closing one sheet and simultaneously opening a dialog).
The page below the sheet is rendered as a blank grey box until the sheet animation finishes, then it displays correctly.
I'm seeing this behaviour on a Z30 running 10.2.1.537
08-29-2014 09:40 AM
08-29-2014 09:51 AM
Yes, I've done that workaround in a few places (e.g. connect(sheet, SIGNAL(closed()), dialog, SLOT(open())).
However, in other places the second action is a few indirect signals away (e.g. finishing a flow in one sheet alters a higher level application state, which causes an existing signal connection to navigate somewhere) and neither page/sheet is aware of the other.
Refactoring in some cases may be possible, but it would increase coupling and duplication (e.g. instead of closing a sheet and navigating to an existing page (which can be triggered from multiple sheets/flows), push the same page inside each of those sheets).
08-29-2014 09:59 AM