我正在向 WindowManager 添加一个 View 并覆盖它的 onConfigurationChanged 函数，如下所示:

查看代码

// onConfigurationChanged should be called after config change has finished
override fun onConfigurationChanged(newConfig: Configuration) {
    super.onConfigurationChanged(newConfig)
    // also tried executing following in the `GlobalLayoutListener` without any difference
    onConfigOrSystemUIChanged(newConfig)
}

fun onConfigOrSystemUIChanged(newConfig: Configuration?) {
    val screen = getScreenSize(this)

    // screen should hold current screen size
    // but this sometimes contains the wrong size, the one from before the config change

    L.d("[%s] Config changed (%s)", logBaseInfo, screen)
}

服务代码

override fun onConfigurationChanged(newConfig: Configuration) {
    super.onConfigurationChanged(newConfig)

    val screen = getScreenSize(this)
    L.d("Config changed in SERVICE: Screen: %s | newConfig: %s", screen, newConfig);
}

问题

我可以看到这在大约 99% 的时间内都有效。我旋转我的设备，将其打开、关闭等等，一切正常。但是我时不时地看到它失败一次，这意味着我的 View 在设备旋转后读取了错误的屏幕尺寸。有什么想法吗？

附加信息 - 日志

我向服务的 onConfigurationChanged 和 View 的 onConfigurationChanged 添加了一些日志。我将 5 个 View 添加到 WindowManager 并查看以下内容:

[OverlayService:168 onConfigurationChanged]: Config changed in SERVICE: Screen: Point(2076, 1080) | newConfig: {0 1.0 themeSeq = 0 showBtnBg = 0 232mcc1mnc [de_AT] ldltr sw360dp w692dp h336dp 480dpi nrml long hdr land finger -keyb/v/h -nav/h appBounds=Rect(144, 0 - 2220, 1080) s.839 mkbd/h desktop/d ?dc}
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 24]] Config changed (Point(2076, 1080))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 26]] Config changed (Point(2076, 1080))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 52]] Config changed (Point(2076, 1080))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 53]] Config changed (Point(2076, 1080))
=> [BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 65]] Config changed (Point(1080, 2076))
// ... here some time that wents by ...
[OverlayService:168 onConfigurationChanged]: Config changed in SERVICE: Screen: Point(1080, 2076) | newConfig: {0 1.0 themeSeq = 0 showBtnBg = 0 232mcc1mnc [de_AT] ldltr sw360dp w360dp h668dp 480dpi nrml long hdr port finger -keyb/v/h -nav/h appBounds=Rect(0, 0 - 1080, 2076) s.840 mkbd/h desktop/d ?dc}
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 26]] Config changed (Point(1080, 2076))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 52]] Config changed (Point(1080, 2076))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 53]] Config changed (Point(1080, 2076))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 65]] Config changed (Point(1080, 2076))
[BaseMviOverlayView:115 onConfigOrSystemUIChanged]: [MviHandleView[Index: 24]] Config changed (Point(1080, 2076))

在这里您看到一个 View (在日志行的开头，第 6 行用 => 标记)确实得到了错误的屏幕尺寸，我没有不知道为什么...

附加信息 - 功能

fun getScreenSize(context: Context) {
    val wm = context.getSystemService(Context.WINDOW_SERVICE) as WindowManager
    val outSize = Point()
    wm.getDefaultDisplay().getSize(outSize)
    return outSize
}

最佳答案

这可能是因为在屏幕旋转尚未完成时测量 View 。尝试设置超时。

clearTimeout(t)
t = setTimeout(function(){/*do your stuff here*/},200);

这里的 t 是一个全局变量——如果屏幕在测量屏幕尺寸之前旋转，则为 clearTimeout。尝试使用以毫秒为单位的时间(在我的代码中为 200)来优化所需的行为。

关于android - WindowManager 中 View 的 onConfigurationChanged 工作不可靠，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/52926334/