Edit Question - KnowledgeHub

Title Body

I've noticed that onLayout and onSizeChanged get called twice in immediate succession after an orientation change, either from landscape->portrait or from portrait->landscape, when handling the configuration change from an Activity. Furthermore, the first onLayout/onSizeChanged contain the old dimensions (before the rotate), while the 2nd onLayout/onSizeChanged contain the new (correct) dimensions. Does anyone know why, and/or how to work around this? It seems like perhaps the screen size change happens quite some time after the configuration change - i.e., the dimensions are not correct immediately after the configuration change when onConfigurationChanged is called? Here's the debug output of the code below, showing both onLayout/onSizeChanged calls after a rotation from Portrait to Landscape (note that the device is 540x960, so the landscape width should be 960 while the portrait width is 540): 03-13 17:36:21.140: DEBUG/RotateTest(27765): onConfigurationChanged: LANDSCAPE 03-13 17:36:21.169: DEBUG/RotateTest(27765): onSizeChanged:540,884,0,0 03-13 17:36:21.189: DEBUG/RotateTest(27765): onLayout:true-0,0,540,884 03-13 17:36:21.239: DEBUG/RotateTest(27765): onSizeChanged:960,464,540,884 03-13 17:36:21.259: DEBUG/RotateTest(27765): onLayout:true-0,0,960,464 Note also that the first onSizeChanged oldwidth and oldheight are 0, indicating that we were just added to the view hierarchy - yet with the wrong dimensions for landscape! And here is the code that illustrates this behavior: MyActivity.java package com.example; import android.app.Activity; import android.content.res.Configuration; import android.os.Bundle; import android.util.Log; import android.widget.FrameLayout; public class MyActivity extends Activity { private static String TAG = "RotateTest"; @Override public void onConfigurationChanged(Configuration newCo

Tags (comma-separated) Cancel