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-19-2012 06:47 PM
I've been trying to dynamically hide/unhide an ActionItem but the 'visible' property doesnot exist for ActionItem...only 'enable' exists which simply grays out the item.
Has anyone been able to hide/unhide action items?
It's a common UI usage on older BB devices to only display meaninful context menus when you select an item in a list for example:
if currently selected item has an address, show the MAPS menu (action item)
but if no address exists, do not show the MAPS menu (action item) as it is useless
09-20-2012 05:36 PM
ActionItems and Tabs don't have a property visible - only enable true/false
there are Issues reported by me in IssueTracker - please vote
09-20-2012 05:53 PM
thanks! i've up-voted your feature request.
i will stick with enable/disable for the time being until this is resolved.
hope that a rim representative here pushes this feature for the next release!!!