Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

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.

Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified
Accepted Solution

VirtualKeyboard.setVisibility() on Storm Simulator

Anybody else working on the Storm simulator having similar issue?


- virtual keyboard gets instantiated (for example, when the user clicks on a text field)


- user exits the screen, but the virtual keyboard remains, even though the old screen called setVisibility(HIDE) from the onClose() method


- when the original calling screen gets focus back, it calls setVisibility(HIDE)


- the calling screen also called setVisibility(HIDE_FORCE) from its constructor


...and yet the keyboard remains on the screen.




Posts: 4,764
Registered: ‎07-21-2008
My Device: Not Specified

Re: VirtualKeyboard.setVisibility() on Storm Simulator

Issue resolved.


Turns out that if you have a Screen implementation that overrides onFocusNotify(), you will keep the framework from clearing the keyboard.


Adding a call to super.onFocusNotify() clears up the issue.