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.
09-20-2013 11:51 AM
Please help me with the problem related to Picture editor, I can not open it on 10.1.0.1020 but working normally on 10.1.1.1483 and above. Below is source code
QVariantMap entry = QVariantMap(); QString size = "250x250"; entry["size"] = size; QString upScale= "false"; entry["upScale"] = upScale; QByteArray encData = bb::PpsObject::encode(entry); iRequest.setData(encData); iRequest.setAction("bb.action.EDIT"); QString mimeT = QString("image/ipg"); iRequest.setMimeType(mimeT); iRequest.setUri("file/accounts/1000/shared/camera/
IMG_00000001.jpg"); iRequest.setTarget("sys.pictureeditor.cardeditor") ; InvokeTargetReply *reply = iManager->invoke(iRequest); iManager->setParent(this);
10-07-2013 11:35 AM
Hi maiakhoa, if it works on a later SDK, then it could have been a bug that got fixed on the 10.1.1.1483 build. Please use the later SDK.