Following is a sample sublayout.
What you have in the layoutMyScreen() method will depend on what you want to do. You could delete all the Fields from the screen and add new ones, or you could replace some Fields whose orientation changes, or you could just update Bitmaps.
In this example, I have assumed that there are Field changes going on that will cause a re-layout of the Screen, so you must do it outside the sublayout() method. It may be possible to do some of these things, for example, update Bitmaps, in sublayout(), however I would not do anything that involves a lot of processing there. For example, I would not resize a Bitmap. If you think you are going to need to resize a Bitmap, you should do it once at screen creation time, not every time your orientation changes.
Note that this is not real code, it is just something I mocked up to explain my suggestion (not compiled or tested in anyway, use at your own risk!). Note that it assumes that layoutMyScreen() updates _displayHeight and _displayWdith and these variables are accessible. This is code like I would put at a Screen level, I suspect you could do similar things at a Manager or Field Level if you wanted, so for example, you could have a Field that updates itself. I've not done that, mainly becuase in the places I need to do this, I've taken a Screen view of the layout. This is probably not the best way, having Fields look after themselves is a much more OO approach. As noted right at the start, I'm not the best UI or even OO programmer on this forum. Others may well have different and I suspect better approaches.
Hope this helps:
protected final void sublayout(int width, int height) {
if ( _displayHeight != Display.getHeight() ||
_displayWdith != Display.getWidth() ) {
UiApplication.getUiApplication().invokeLater(new Runnable() {
public void run() {
layoutMyScreen();
}
};
}
super.sublayout(width, height);
}
