显示ProgressDialog之前的setRequestedOrientation会导致崩溃

Question

我正在开发一个Android应用程序,它应该只在纵向模式下运行,因为布局不适合手机的横向屏幕.但是,在平板电脑和上网本上,我希望该应用仅以横向模式运行.

我现在尝试检查应用程序是否在平板电脑设备上运行,并通过setRequestedOrientation设置相应的请求方向.

问题是,当设备尚未处于我正在请求的方向时,应用程序崩溃了,因为我在调用setRequestedOrientation之后不久显示了progressDialog,这似乎泄漏了一个窗口.

Logcat说:

10-18 21:15:30.698: E/WindowManager(653): Activity has leaked window  com.android.internal.policy.impl.PhoneWindow$DecorView@41991418 that was originally added here
10-18 21:15:30.698: E/WindowManager(653): android.view.WindowLeaked: Activity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@41991418 that was originally added here
10-18 21:15:30.698: E/WindowManager(653):   at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:279)
10-18 21:15:30.698: E/WindowManager(653):   at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:215)
10-18 21:15:30.698: E/WindowManager(653):   at android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:140)
10-18 21:15:30.698: E/WindowManager(653):   at android.view.Window$LocalWindowManager.addView(Window.java:537)
10-18 21:15:31.888: E/WindowManager(653): Activity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@41588040 that was originally added here
10-18 21:15:31.888: E/WindowManager(653): android.view.WindowLeaked: Activity has leaked window com.android.internal.policy.impl.PhoneWindow$DecorView@41588040 that was originally added here
10-18 21:15:31.888: E/WindowManager(653):   at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:279)
10-18 21:15:31.888: E/WindowManager(653):   at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:215)
10-18 21:15:31.888: E/WindowManager(653):   at android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:140)
10-18 21:15:31.888: E/WindowManager(653):   at android.view.Window$LocalWindowManager.addView(Window.java:537)
10-18 21:15:34.168: E/AndroidRuntime(653):  at android.view.WindowManagerImpl.findViewLocked(WindowManagerImpl.java:599)
10-18 21:15:34.168: E/AndroidRuntime(653):  at android.view.WindowManagerImpl.removeView(WindowManagerImpl.java:336)
10-18 21:15:34.168: E/AndroidRuntime(653):  at android.view.WindowManagerImpl$CompatModeWrapper.removeView(WindowManagerImpl.java:151)

我该怎么做才能防止这次崩溃？任何帮助将受到高度赞赏.

编辑:由于我无法解决这个问题,我终于设法编辑了我的布局,现在它允许在纵向和横向模式下使用.

Answer 1

你有可以显示的源代码吗？这可以帮助确定问题.

我实际上有同样的问题.但这只发生在我的一些活动上.

当屏幕方向改变时,Android实际上会破坏并重新创建活动.

所以,我的代码看起来像这样.

   @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        this.setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);

        setContentView(R.layout.displayscreen);

        bottomButton = (Button) findViewById(R.id.bottomButton);
        bottomButton.setOnClickListener(bottomButtonClick);
        bottomButton.setTypeface(font);
        bottomButton.setTextSize(16);
}

看看发生的事情是视图没有正确附加到窗口管理器.所以我认为oncreate可能不是最好的选择.

相反,我把它添加到我的简历上,它的工作原理.像这样:

   @Override
    public void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.displayscreen);

        bottomButton = (Button) findViewById(R.id.bottomButton);
        bottomButton.setOnClickListener(bottomButtonClick);
        bottomButton.setTypeface(font);
        bottomButton.setTextSize(16);
}

@Override
protected void onResume() {
    super.onResume();
    this.setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_PORTRAIT);
}

不幸的是,这也导致活动仍然被破坏并重新创建.调用onCreate和onResume两次......不对不错？

所以要解决这个问题.您必须将此添加到您的活动的Android清单中.

android:configChanges="keyboardHidden|orientation"

一个例子:

<activity 
    android:name="com.Test.Info.DisplayInfo"
    android:configChanges="keyboardHidden|orientation"
    android:label="@string/info">
</activity>

此代码可防止销毁/重新创建循环.

希望这有帮助!

干杯

Answer 2

如果你使用

setRequestedOrientation(SCREEN_ORIENTATION_NOSENSOR);

临时锁定,和

setRequestedOrientation(ActivityInfo.SCREEN_ORIENTATION_SENSOR);

解锁屏幕旋转,也许你遇到了以下问题.

如果您使用此方法锁定屏幕方向并且设备未处于默认方向,则它将切换到默认方向,销毁并创建您的活动.您的应用程序将崩溃,因为您尝试更新一些失败的progressDialog.