Therefore, we need to find a solution to solve the stuttering problem caused by the conflict of motion effects.
The root cause of this problem can be briefly described as: uncontrollable dynamic conflict (business randomness) + main thread time-consuming method that cannot be placed (pop-up window instantiation, view infalte). We simulate the ongoing motion effects of the App (such as page switching) with horizontally moving blocks it can be seen that when the Snackabr pop-up window pops up, the block motion is obviously stuck (moving to about 1/3). When the pop-up window pops up, if the app happens to also have animation effects, the main thread may draw two animation effects at the same time, which will cause a freeze, as shown in the figure below. Due to the requirements of the business scenario, for the App, the popup timing of the SDK's popup window is random. Background and ProblemsĪ certain SDK has PopupWindow and dynamic effects. 对应的三个方法，继续看 WindowManager 对应的具体实现类， WindowManagerImple void View view, ViewGroup.LayoutParams params) 更新过程 public void updateViewLayout(View view, ViewGroup.Author: vivo Internet front-end team - Zhang Xichen 1. Public void updateViewLayout(View view, ViewGroup.LayoutParams params) Public void addView(View view, ViewGroup.LayoutParams params) view The view to be added to this params The LayoutParams to assign to view.secondary Display} and the specified display can't be found.errors, such as adding a second view to a window without removing the first view.Assign the passed LayoutParams to the passed View and add the view to the window.Of this class, call #getSystemService() Context.getSystemService()}. Window 的添加、删除、更新 view 均是通过 WindowManager 来完成的，而 WindowManager 继承了 ViewManager 的接口 /** Interface to let you add and remove child views to an Activity. WindowManagerService window 的具体实现位于 WindowManagerService 中， WindowManager 和 WindowManagerService 联系。 WindowManager WindowManager 是 外界访问 Window Window 也是一个抽象的概念，每个 window 内对应这一个 DecorView 和一个 ViewRootImpl ， window 和 DecorView 通过 ViewRootImpl
0 kommentar(er)
