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.
05-25-2009 03:07 PM
I have some custom Fields that paint blocks of text in a scrolling VerticalFieldManager. These fields are focusable since they expand/contract in size when they recieve a navigationClick event. When a given field is expanded, the user may need to scroll down in order to read the entire contents. All of this works fine, except that when you touch the custom field in order to scroll down the screen, the internal method moveFocusToFieldWithInput is called which resets the screen position to the TOP of the currently focused field. Is there a way to change this behavior? The user needs to be able to scroll down the VerticalFieldManager and touch fields in the process without the focus being reset to the top of the field. I have look at trying to override all focus related fields, including moveFocus on the VFM and the screen, but none seem to alter this behavior.
05-25-2009 03:22 PM
06-21-2010 05:16 PM
06-22-2010 10:24 AM
No, I never found a solution to this. The workaround was to refactor the code to use a focusable ActiveRichTextField which magically does not seem to have this problem.