Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I don't think it is possible to do anything but guess at your problem without looking at your code. But whatever your problem is, I am confident that it is based on a misunderstanding of how to use Managers within a Screen. So I recommend that you review the following articles to improve your knowledge in this area and so hopefully resolve the problem yourself:</p> <p>Start here: <a href="http://developer.blackberry.com/bbos/java/documentation/intro_to_ui_1969897_11.html" rel="nofollow">UI Introduction</a> This provides the Background around Managers and Fields. </p> <p>Then read this article: <a href="http://supportforums.blackberry.com/t5/Java-Development/MainScreen-explained/ta-p/606644" rel="nofollow">MainScreen Explained</a></p> <p>I suspect as a result of reading this article, you may be able to discard your 'title bar' and use setTitle() or setBanner() to provide this function. </p> <p>I hope this resolves your problems.</p> <p>A few other points:</p> <p>In all my years of BB programming, I have never had to use doPaint() to get something painting the way I wanted. I can't think of a situation that this will in fact help. So if you think you need it, try invalidate() instead. </p> <p>I have used invalidate() when I making a change to the Field that will change its on screen appearance (but not its size). I have used it in a scroll change listener. But it is a method of last resort. </p> <p>Remember that LabelFields are not focusable, so in OS's before 6, that made them a problem to scroll. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload