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.
12-01-2010 10:21 PM
Dialogs are using native code of PlayBook they won't work on Desktop, was this is everybody's issue? Or people having this error on Simulator?
12-01-2010 10:24 PM
12-02-2010 05:46 AM
@elena : I having trouble with Desktop Air application, no problem with the simulator.
Is there a way to know which part of the qnx framework don't work on desktop since you point the fact that Dialogs call playbook's native code ?
12-02-2010 08:35 AM
12-03-2010 09:59 AM
In listening to the MAX 2010 presentation found here
Under Dialogs, it talsk about that the Dialog classes communicate to a service that displays the dialog and it is not a part of the application display list. this may explain why this and other singleton classes crash on the AIR side, since those services are not running.
For this to probably work as an AIR application to help speed development, they would have to supply a runtime service to respond to these types of requests, or proxy it out to simulate the same behavior. I vote (if I had one) for a service/application that can respond to Alerts, simulate other services like batter changes, swipes, accelerometer, geolocation, etc. Simple AIR application with inter-process communication would make this possible.