If the Activity is onBackground, the view is hidden as well.įor SDK 24 and 26, the TYPE_APPLICATION_OVERLAY view lives outside the Activity view boundary. TYPE_APPLICATION_OVERLAY/TYPE_SYSTEM_ALERT launched through Activity behaviorįor SDK 14 the TYPE_SYSTEM_ALERT view lives within the Activity view boundary. I tested on SDK 16 (Jelly Bean), 24 (Nougat), and 26 (Oreo) TYPE_APPLICATION_OVERLAY/TYPE_SYSTEM_ALERT view lifeįor SDK 14 and 24, the view is killed as well, when the App is killed (manually).įor SDK 26, the View lives on even when the App is killed (manually), regardless if the View is launched through Service or Activity. But it is worth to note my findings below as reference, to ensure support across devices is tested thoroughly. I’m not 100% sure if this is the emulator settings. private val windowManager by lazy Add the View to WindowManagerĪfter the above has been achieved, one would just need to add the view to the WindowManager windowManager.addView(floatView, paramFloat)įrom my experience on the Views added through WindowManager, I got different behavior in different SDK. However, if you work outside the Activity (in another class or Service), you could access the WindowManager using the Context. Access the WindowManagerīy default, you could get the WindowManager object in the Activity.
With that, we could code something beyond the conventional Android App interface.īelow is the example code (available below) I made to demonstrate how we could have a view outside of our Activity.īelow is what is required to code it. The fun of WindowManager is the ability to have a View that is on top of the Activity. Let’s experiment some view on WindowManger
This enables one to display a view on top of the Activity! Among other things, it automatically performs window transitions and animations when opening or closing an app or rotating the screen. The Android WindowManager is a system service, which is responsible for managing the z-ordered list of windows, which windows are visible, and how they are laid out on screen. However, it is a useful system service.Īs explained nicely in this stackoverflow, For conventional Android development learning, WindowManager is not something typically taught.
0 kommentar(er)
