Android窗口类型

Android 9.0系统源码_窗口管理(二)WindowManager对窗口的管理过程 通过Android9系统源码分析WindowManager添加系统状态栏窗口过程 阅读详情

WindowManager会根据窗口的类型来决定Z-Order,通过Z-Order也就决定了窗口从上到下的显示顺序。下表个表明了窗口类型与Z-Order的关系。表中layer值越大表示窗口越靠上。


System

NO.WINDOW TYPE描述LAYER是否HIDE
1TYPE_UNIVERSE_BACKGROUNDBehind the universe of the real windows.
In multiuser systems shows on all users' windows.
1hide
2TYPE_PRIVATE_PRESENTATIONWindow for Presentation on top of private virtual display.2
3TYPE_WALLPAPERwallpaper window, placed behind any window that wants
 to sit on top of the wallpaper. In multiuser systems shows only on the owning user's window.wallpaper is at the bottom, though the window manager may move it.
2
4TYPE_PHONEThese are non-application windows providing user interaction with the phone (in particular incoming calls).These windows are normally placed above all applications, but behind the status bar.In multiuser systems shows on all users' windows.3
5TYPE_SEARCH_BARthe search bar.  There can be only one search bar window; it is placed at the top of the screen.
In multiuser systems shows on all users' windows.
4
6TYPE_RECENTS_OVERLAY Same layer as {@link #TYPE_SYSTEM_DIALOG} but only appears on one user's screen.In multiuser systems shows on all users' windows.5hide
7TYPE_SYSTEM_DIALOGpanel that slides out from the status bar In multiuser systems shows on all users' windows.5
8TYPE_TOASTtransient notifications. In multiuser systems shows only on the owning user's window.toasts and the plugged-in battery thing6
9TYPE_PRIORITY_PHONEpriority phone UI, which needs to be displayed even if the keyguard is active.  These windows must not take input focus, or they will interfere with the keyguard. In multiuser systems shows on all users' windows.SIM errors and unlock.  Not sure if this really should be in a high layer.7
10TYPE_DREAMDreams (screen saver) window, just above keyguard. In multiuser systems shows only on the owning user's window.used for Dreams (screensavers with TYPE_DREAM windows)8hide
11TYPE_SYSTEM_ALERTsystem window, such as low power alert. These windows are always on top of application windows. In multiuser systems shows only on the owning user's window.like the ANR / app crashed dialogs9
12TYPE_INPUT_METHODinternal input methods windows, which appear above the normal UI.  Application windows may be resized or panned to keep the input focus visible while this window is displayed. In multiuser systems shows only on the owning user's window. on-screen keyboards and other such input method user interfaces go here.10
13TYPE_INPUT_METHOD_DIALOGinternal input methods dialog windows, which appear above the current input method window. In multiuser systems shows only on the owning user's window.on-screen keyboards and other such input method user interfaces go here.11
14TYPE_KEYGUARD_SCRIMkeyguard scrim window. Shows if keyguard needs to be restarted.In multiuser systems shows on all users' windows. the safety window that shows behind keyguard while keyguard is starting12hide
15TYPE_KEYGUARDkeyguard window.In multiuser systems shows on all users' windows. the keyguard; nothing on top of these can take focus, since they are responsible for power management when displayed.13
16TYPE_KEYGUARD_DIALOGdialogs that the keyguard shows In multiuser systems shows on all users' windows.14
17TYPE_STATUS_BAR_SUB_PANELpanel that slides out from under the status bar In multiuser systems shows on all users' windows.15hide
18TYPE_STATUS_BARthe status bar.  There can be only one status bar window; it is placed at the top of the screen, and all other windows are shifted down so they are below it. In multiuser systems shows on all users' windows.16
19TYPE_STATUS_BAR_PANELpanel that slides out from over the status bar In multiuser systems shows on all users' windows.17
20TYPE_VOLUME_OVERLAYThe volume level overlay/dialog shown when the user
changes the system volume. In multiuser systems shows on all users' windows.the on-screen volume indicator and controller shown when the user changes the device volume
18hide
21TYPE_SYSTEM_OVERLAYsystem overlay windows, which need to be displayed on top of everything else.  These windows must not take input focus, or they will interfere with the keyguard. In multiuser systems shows only on the owning user's window.the on-screen volume indicator and controller shown when the user changes the device volume19
22TYPE_NAVIGATION_BARNavigation bar (when distinct from status bar) In multiuser systems shows on all users' windows.the navigation bar, if available, shows atop most things20hide
23TYPE_NAVIGATION_BAR_PANELNavigation bar panel (when navigation bar is distinct from status bar) In multiuser systems shows on all users' windows. some panels (e.g. search) need to show on top of the navigation bar21hide
24TYPE_SYSTEM_ERRORinternal system error windows, appear on top of everything they can.In multiuser systems shows only on the owning user's window.system-level error dialogs22
25TYPE_MAGNIFICATION_OVERLAYMagnification overlay window. Used to highlight the magnified portion of a display when accessibility magnification is enabled.In multiuser systems shows on all users' windows.used to highlight the magnified portion of a display23hide
26TYPE_DISPLAY_OVERLAYDisplay overlay window.  Used to simulate secondary display devices.In multiuser systems shows on all users' windows.used to simulate secondary display devices24hide
27TYPE_DRAGthe drag-and-drop pseudowindow.  There is only one drag layer (at most), and it is placed on top of all other windows.In multiuser systems shows only on the owning user's window.the drag layer: input for drag-and-drop is associated with this window,which sits above all other focusable windows25hide
28TYPE_SECURE_SYSTEM_OVERLAYsecure system overlay windows, which need to be displayed on top of everything else.  These windows must not take input focus, or they will interfere with the keyguard.This is exactly like {@link #TYPE_SYSTEM_OVERLAY} except that only the system itself is allowed to create these overlays.  Applications cannotobtain permission to create secure system overlays.In multiuser systems shows only on the owning user's window.26hide
29TYPE_BOOT_PROGRESSThe boot progress dialog, goes on top of everything in the world.In multiuser systems shows on all users' windows.27hide
30TYPE_POINTER(mouse) pointer In multiuser systems shows on all users' windows.the (mouse) pointer layer28hide
31TYPE_HIDDEN_NAV_CONSUMERFake window to consume touch events when the navigation
 bar is hidden. In multiuser systems shows on all users' windows.
29hide

Application

NO.WINDOW TYPE描述LAYER是否HIDE
1FIRST_APPLICATION_WINDOWStart of window types that represent normal application windows.2
2TYPE_BASE_APPLICATIONan application window that serves as the "base" window
 of the overall application; all other application windows will appear on top of it.In multiuser systems shows only on the owning user's window.
2
3TYPE_APPLICATIONa normal application window.  The {@link #token} must be an Activity token identifying who the window belongs to. In multiuser systems shows only on the owning user's window.2
4TYPE_APPLICATION_STARTINGspecial application window that is displayed while the application is starting.  Not for use by applications themselves;this is used by the system to display something until the application can show its own windows.In multiuser systems shows on all users' windows.2
5LAST_APPLICATION_WINDOWEnd of types of application windows.2

Sub Window

NO.WINDOW TYPE描述LAYER是否HIDE
1FIRST_SUB_WINDOWStart of types of sub-windows.  The {@link #token} of these windows must be set to the window they are attached to.  These types of windows are kept next to their attached window in Z-order, and their coordinate space is relative to their attached window.1
2TYPE_APPLICATION_PANELa panel on top of an application window.  These windows
 appear on top of their attached window.
1
3TYPE_APPLICATION_ATTACHED_DIALOGlike {@link #TYPE_APPLICATION_PANEL}, but layout of the window happens as that of a top-level window, as a child of its container.1
4TYPE_APPLICATION_MEDIAwindow for showing media (such as video).  These windows are displayed behind their attached window.1
5TYPE_APPLICATION_SUB_PANELa sub-panel on top of an application window.  These windows are displayed on top their attached window and any {@link #TYPE_APPLICATION_PANEL} panels.2
6TYPE_APPLICATION_MEDIA_OVERLAYwindow for showing overlays on top of media windows. These windows are displayed between TYPE_APPLICATION_MEDIA and the application window.  They should be translucent to be useful.  This is a big ugly hack so:-1hide
Sub Window对应的主窗口为0

Media Sublayer(-2) < Media Overlay sublayer (-1) < Main Layer(0) < Attached Dialog (1) < Sub panel Sublayer (2)

子窗口与父窗口共用一个token。的父窗口一般是所在的Activity,比如surfaceView是一个子窗口,他的父窗口是所在activity所在的window。


窗口类型与Layer转换的函数为windowTypeToLayerLw

/frameworks/base/policy/src/com/android/internal/policy/impl/PhoneWindowManager.java

public int windowTypeToLayerLw(int type) {
        if (type >= FIRST_APPLICATION_WINDOW && type <= LAST_APPLICATION_WINDOW) {
            return 2;
        }
        switch (type) {
        case TYPE_UNIVERSE_BACKGROUND:
            return 1;
        case TYPE_WALLPAPER:
            // wallpaper is at the bottom, though the window manager may move it.
            return 2;
        case TYPE_PHONE:
            return 3;
        case TYPE_SEARCH_BAR:
            return 4;
        case TYPE_RECENTS_OVERLAY:
        case TYPE_SYSTEM_DIALOG:
            return 5;
        case TYPE_TOAST:
            // toasts and the plugged-in battery thing
            return 6;
        case TYPE_PRIORITY_PHONE:
            // SIM errors and unlock.  Not sure if this really should be in a high layer.
            return 7;
        case TYPE_DREAM:
            // used for Dreams (screensavers with TYPE_DREAM windows)
            return 8;
        case TYPE_SYSTEM_ALERT:
            // like the ANR / app crashed dialogs
            return 9;
        case TYPE_INPUT_METHOD:
            // on-screen keyboards and other such input method user interfaces go here.
            return 10;
        case TYPE_INPUT_METHOD_DIALOG:
            // on-screen keyboards and other such input method user interfaces go here.
            return 11;
        case TYPE_KEYGUARD:
            // the keyguard; nothing on top of these can take focus, since they are
            // responsible for power management when displayed.
            return 12;
        case TYPE_KEYGUARD_DIALOG:
            return 13;
        case TYPE_STATUS_BAR_SUB_PANEL:
            return 14;
        case TYPE_STATUS_BAR:
            return 15;
        case TYPE_STATUS_BAR_PANEL:
            return 16;
        case TYPE_VOLUME_OVERLAY:
            // the on-screen volume indicator and controller shown when the user
            // changes the device volume
            return 17;
        case TYPE_SYSTEM_OVERLAY:
            // the on-screen volume indicator and controller shown when the user
            // changes the device volume
            return 18;
        case TYPE_NAVIGATION_BAR:
            // the navigation bar, if available, shows atop most things
            return 19;
        case TYPE_NAVIGATION_BAR_PANEL:
            // some panels (e.g. search) need to show on top of the navigation bar
            return 20;
        case TYPE_SYSTEM_ERROR:
            // system-level error dialogs
            return 21;
        case TYPE_MAGNIFICATION_OVERLAY:
            // used to highlight the magnified portion of a display
            return 22;
        case TYPE_DISPLAY_OVERLAY:
            // used to simulate secondary display devices
            return 23;
        case TYPE_DRAG:
            // the drag layer: input for drag-and-drop is associated with this window,
            // which sits above all other focusable windows
            return 24;
        case TYPE_SECURE_SYSTEM_OVERLAY:
            return 25;
        case TYPE_BOOT_PROGRESS:
            return 26;
        case TYPE_POINTER:
            // the (mouse) pointer layer
            return 27;
        case TYPE_HIDDEN_NAV_CONSUMER:
            return 28;
        }
        Log.e(TAG, "Unknown window type: " + type);
        return 2;
    }


    public int subWindowTypeToLayerLw(int type) {
        switch (type) {
        case TYPE_APPLICATION_PANEL:
        case TYPE_APPLICATION_ATTACHED_DIALOG:
            return APPLICATION_PANEL_SUBLAYER;
        case TYPE_APPLICATION_MEDIA:
            return APPLICATION_MEDIA_SUBLAYER;
        case TYPE_APPLICATION_MEDIA_OVERLAY:
            return APPLICATION_MEDIA_OVERLAY_SUBLAYER;
        case TYPE_APPLICATION_SUB_PANEL:
            return APPLICATION_SUB_PANEL_SUBLAYER;
        }
        Log.e(TAG, "Unknown sub-window type: " + type);
        return 0;
    }

1).  Window类的基本属性如下:

          FEATURE_OPTIONS_PANEL = 0;                      可选的Panel标志(默认使能)
          FEATURE_NO_TITLE = 1;                                 无标题栏
          FEATURE_PROGRESS = 2;                                 标题栏上显示加载进度,如webview加载网页时(条状进度条)
          FEATURE_LEFT_ICON = 3;                                标题栏左侧显示一个图标
          FEATURE_RIGHT_ICON = 4;                              标题栏右侧显示一个图标
          FEATURE_INDETERMINATE_PROGRESS = 5;   不确定的进度(圆圈状等待图标)
          FEATURE_CONTEXT_MENU = 6;                        Menu菜单(默认使能)
          FEATURE_CUSTOM_TITLE = 7;                          自定义标题栏,该属性不能与其他标题栏属性合用
          FEATURE_ACTION_BAR = 8;                               ActionBar属性,ActionBar显示的,TitleBar就没有啦                                                             

          FEATURE_ACTION_BAR_OVERLAY = 9;            覆盖在内容之上的ActionBar

          FEATURE_ACTION_MODE_OVERLAY = 10;        AcitionBar的覆盖在内容的模式

          FEATURE_OPENGL = 8;                                       若开启OpenGL,那么2D将由OpenGL处理(OpenGL中2D是3D的子集)
          PROGRESS_VISIBILITY_ON = -1;                         进度条可见
          PROGRESS_VISIBILITY_OFF = -2;                       进度条不可见
          PROGRESS_INDETERMINATE_ON = -3;              开启不确定模式
          PROGRESS_INDETERMINATE_OFF = -4;             关闭不确定模式
          PROGRESS_START = 0;                                        第一进度条的最小值
          PROGRESS_END = 10000;                                     第一进度条的最大值
          PROGRESS_SECONDARY_START = 20000;          第二进度条的最小值
          PROGRESS_SECONDARY_END = 30000;              第二进度条的最大值

       经常使用到的:

    1、隐藏标题栏

        requestWindowFeature(Window.FEATURE_NO_TITLE);

    2、在标题栏显示进度条

        requestWindowFeature(Window.FEATURE_PROGRESS);

        setContentView(R.layout.progressbar_1);

        setProgressBarVisibility(true);

        final ProgressBar progressHorizontal = (ProgressBar)findViewById(R.id.progress_horizontal);

        setProgress(progressHorizontal.getProgress() * 100);

        setSecondaryProgress(progressHorizontal.getSecondaryProgress()* 100);

    3、使用自定义标题栏

        requestWindowFeature(Window.FEATURE_CUSTOM_TITLE);

        setContentView(R.layout.xxx);

        getWindow().setFeatureInt(Window.FEATURE_CUSTOM_TITLE,R.layout.my_title_bar);

    4、清除标题栏内容,而区域保留

        ((ViewGroup)getWindow().findViewById(com.android.internal.R.id.title_container)).removeAllViews();

    5、隐藏标题栏

        ((ViewGroup)getWindow(). findViewById(com.android.internal.R.id.title_container)).setVisibility(View.GONE);

    6、显示标题栏

        ((ViewGroup)getWindow(). findViewById(com.android.internal.R.id.title_container)).setVisibility(View.VISIBLE);

    注意事项

    (1) requestWindowFeature()要在setContentView()之前调用;

    (2) 设置各种Feature,是具有排它性的,一旦设置,后续不可更改为别的类型;

    (3)当使用TabHost(由ActivityGroup派生)时,各个Tab里的Activity,要么都是NO_TITLE,要么都是CUSTOM_TITLE,无法分别进行设置

    ID_ANDROID_CONTENT = com.android.internal.R.id.content;  就是显示内容的id。


    2). Window类的内部类接口Callback包含一系列dispatchXxxx函数和一系列onXxxx函数,用于处理UI事件

        public boolean dispatchKeyEvent(KeyEvent event);

        public boolean dispatchKeyShortcutEvent(KeyEvent event);

        public boolean dispatchTouchEvent(MotionEvent event);

        public boolean dispatchTrackballEvent(MotionEvent event);

        public boolean dispatchGenericMotionEvent(MotionEvent event);                            移动事件

        public boolean dispatchPopulateAccessibilityEvent(AccessibilityEvent event);

        public View onCreatePanelView(int featureId);

        public boolean onCreatePanelMenu(int featureId, Menu menu);

        public boolean onPreparePanel(int featureId, View view, Menu menu);

        public boolean onMenuOpened(int featureId, Menu menu);                                      用户选择菜单项。

        public boolean onMenuItemSelected(int featureId, MenuItem item);                          用户选择菜单项。

        public void onWindowAttributesChanged(WindowManager.LayoutParams attrs);        当前窗口属性改变。

        public void onContentChanged();                                  窗口的view发生改变。

        public void onWindowFocusChanged(boolean hasFocus);窗口的焦点发生变换

        public void onAttachedToWindow();                              窗口附加到窗口管理器上。

        public void onDetachedFromWindow();                          窗口从窗口管理器上摘除。

        public void onPanelClosed(int featureId, Menu menu);

        public boolean onSearchRequested();                       当用户按下了search按钮。如果启动了搜索界面则返回true,如果不能执行则返回false。

        public ActionMode onWindowStartingActionMode(ActionMode.Callback callback);

        public void onActionModeStarted(ActionMode mode);

        public void onActionModeFinished(ActionMode mode);

Android 12 应用兼容性适配指导 Android 12 应用兼容性适配指导 一、兼容性调试工具 Android 11开始引入了新的工具,可针对Android新平台中的行为变更进行测试和调试。这些工具是兼容性框架的一部分,该框架使得开发者可通过开发者选项或adb命令单独打开和关闭各项变更。藉此,可在最新android预览版中测试我们的app受到新平台及target api调整的影响,完成app对新平台的兼容适配。 使用adb命令打开或关闭变更,请运行以下命令之一: adb shell am compat enable (C.. 阅读详情

相关推荐

SystemUI中新添加Window(屏保)与导航栏交互出现的常见问题

不积跬步无以至千里 最近项目项目里添加了屏保功能,屏保实际为锁屏或者屏幕休眠,出现的一个Window,此用以显示时间与通知的重要信息,并具有省电模式的一个界面。 这一块的实现主要是通过添加一个Window,此Window的层级位于锁屏之上,但是又要低于一些系统重要的弹窗Window(比如调节音量、PowerUI重启的等等),因此此处挑选了Window层级为 WindowManager.LayoutParams.TYPE_STATUS_BAR_PANEL,但是其层级是低于导航栏的等级的 Win...

Older_Fisher的博客 493

Android 窗口常见参数汇总

Window类中有一个WindowManager.LayoutParams类型的属性mWindowAttributes记录了当前窗口的相关参数

yimelancholy的博客 5266

点云配准实战:用DGCNN+Transformer+SVD搞定3D模型对齐(附PyTorch代码)

本文详细介绍了基于深度学习的点云配准实战方法,重点解析了Deep Closest Point (DCP)模型。该模型融合了DGCNN、Transformer和可微分SVD三大核心模块,能够端到端地预测点云间的刚性变换,有效克服传统ICP算法对初始位置敏感、易陷入局部最优的缺点。文章提供了完整的PyTorch代码实现、ModelNet40数据集处理、训练策略及显存优化技巧,旨在帮助开发者在机器人、自动驾驶等领域实现精准的3D模型对齐。

weixin_29061041的博客 155

android 浮窗示例代码,Android 浮窗开发之窗口层级(示例代码)

很多人都知道如何去实现一个简单的浮窗,但是却很少有人去深入的研究背后的流程机制,由于项目中浮窗交互比较复杂,遇到了些坑查看了很多资料,故总结浮窗涉及到的知识点:窗口层级关系(浮窗是如何“浮”的)?浮窗有哪些限制,如何越过用户授权实现浮窗功能?窗口与用户输入系统(Activity是如何接收到touch事件?)。本章我们来研究第一个问题:浮窗为何会浮。 浮窗之所以叫浮窗,是因为它能悬浮于应用或者桌面窗...

weixin_33158453的博客 709

保姆级教程:Synology NAS共享文件夹从创建到权限设置的完整流程

本文提供了一份详尽的Synology NAS共享文件夹创建与权限设置指南。重点讲解了如何将NAS接入企业AD域,并利用域管理员账户进行集中身份验证和权限管理。文章从基础概念、域环境配置、文件夹创建、精细化权限分配到客户端访问与维护,完整覆盖了构建安全高效企业级文件共享空间的全流程,旨在帮助管理员实现便捷的团队协作与数据安全管理。

u9v0w的博客 559

别再为SCI论文配图发愁了!手把手教你用PS+AI搞定从数据图到模式图的全流程

本文详细解析了如何利用Photoshop(PS)和Illustrator(AI)高效完成SCI论文配图的全流程,涵盖数据可视化、模式图设计及期刊适配性输出。通过实战案例,帮助科研人员掌握位图与矢量图的处理技巧,提升论文配图质量,满足不同期刊的出版要求。

weixin_28630185的博客 386

android 窗口类型分析

1, 概述 Android窗口类型主要分成了三大类: 1,应用程序窗口。一般应用程序的窗口,比如我们应用程序的Activity的窗口。 2,子窗口。一般在Activity里面的窗口,比如各种菜单等。 3,系统窗口。系统的窗口,比如输入法,Toast,墙纸等。 WindowManager里面窗口的type类型值定义是一个递增保留的连续增大数值。其实就是窗口的Z-ORDER序列(值越大显示的

Jack的博客 4071

BQ4050开发进阶(二):Protections参数优化策略与实战解析

本文深入解析了BQ4050电池管理芯片中Protections参数的优化策略与实战方法。针对电压、电流、温度等核心保护功能,详细阐述了如何根据具体电芯特性、负载场景和环境因素,精细调整CUV、COV、OCC/OCD等阈值与延时,以在确保电池绝对安全的前提下,实现极致的用户体验与系统可靠性。

rgv234567的博客 487

Android WindowManager窗口类型

WindowManager的LayoutParams中窗口类型与定义: frameworks\base\core\java\android\view\WindowManager.java /** Start of window types that represent normal application windows. ZMS:首个普通应用窗口 */ public static final int FIRST_APPLICATION_WINDOW = 1; /** Window t

m0_70082867的博客 538

麒麟系统下PaddleOCR的离线部署实战:从环境搭建到模型优化

本文详细介绍了在国产麒麟操作系统上离线部署百度PaddleOCR的完整实战流程。从系统环境准备、Conda虚拟环境搭建,到PaddlePaddle框架和PaddleOCR的离线安装,再到预训练模型的本地部署与优化技巧,提供了全面的文字识别解决方案。重点解决了离线环境下依赖包管理、模型量化加速等核心问题,并附带了批量处理与内存监控的进阶代码,适用于对数据安全有严格要求的政务、金融等场景。

docker7nomad的博客 964

【STM32+K210项目】基于K210智能人脸识别+车牌识别系统(完整工程资料源码)

随着时代的进步和科技的迅猛发展,人们对居住安全的重视程度不断提升,对安全防范系统的需求也日益增强。在安防系统中,门禁系统占据着重要的位置。传统的门禁控制方式主要依靠钥匙、密码和门禁卡等,这些方式易于被破解和复制,安全性较低。然而,近年来,生物识别技术的迅速发展和成熟,为解决这一问题提供了新的方案。生物识别技术具备便携性、非易失性、不易遗忘以及难以盗用等优点,逐渐被引入到门禁系统中。传统的小区门禁系统往往依赖人工管理,存在一定的局限性,难以满足用户多样化的需求,也浪费了人力资源。

嵌入式技术开发 1万+

android 入门 博客,Android入门之窗口类型

从WmS的角度看,一个窗口并不是Window类,而是一个View类。WmS收到用户消息后,需要把消息派发到窗口,View类本身并不能直接接收WmS传递过来的消息,真正接收用户消息的必须是IWindow类,而实现IWindow类的是ViewRoot.W类,每一个W内部都包含了一个View变量。WmS并不介意该窗口(View)是属于哪个应用程序的,WmS会按一定的规则判断哪个窗口处于活动状态,然后把用...

weixin_39620984的博客 294

Unity零基础到入门 ☀️| 小万字教程 对 Unity 中的 协程 ❤️全面解析+实战演练❤️

Unity,为了让Unity基础知识专栏更加完善,又肝了一篇协程来学习。 协程在Unity中还是很常用的,一起来看一下协程的基本概念和使用方法吧!

努力前行,总会成为自己心中的那道光 8万+

android 窗口类型介绍

从WmS的角度看,一个窗口并不是Window类,而是一个View类。WmS收到用户消息后,需要把消息派发到窗口,View类本身并不能直接接收WmS传递过来的消息,真正接收用户消息的必须是IWindow类,而实现IWindow类的是ViewRoot.W类,每一个W内部都包含了一个View变量。         WmS并不介意该窗口(View)是属于哪个应用程序的,WmS会按一定的规则判断哪个窗

成长的味道 1231

【100%通过率】华为OD机试真题 Python【数字最低位排序】【最低位排序】

2023华为OD机试真题 Python【数字最低位排序】【最低位排序】 给定一个非空数组(列表) 起元素数据类型为整型 请按照数组元素十进制最低位从小到大进行排序 十进制最低位相同的元素,相对位置保持不变 当数组元素为负值时,十进制最低为等同于去除符号位后对应十进制值最低位

MISAYAONE的博客 1902

Statistics and Machine Learning Toolbox

Statistics and Machine Learning Toolbox(带书签),MATLAB统计学习工具

Android窗口类型有关

从WmS的角度看,一个窗口并不是Window类,而是一个View类。WmS收到用户消息后,需要把消息派发到窗口,View类本身并不能直接接收WmS传递过来的消息,真正接收用户消息的必须是IWindow类,而实现IWindow类的是ViewRoot.W类,每一个W内部都包含了一个View变量。 WmS并不介意该窗口(View)是属于哪个应用程序的,WmS会按一定的规则判断哪个窗口处于活动状态,然后

随手记两笔 704

霍尼韦尔SoftMaster使用说明

霍尼韦尔SoftMaster使用说明

Android WindowManager窗口类型,Android架构师教你如何突破瓶颈

as a child of its container. ZMS:OptionMenu、ContextMenu的默认类型 */ public static final int TYPE_APPLICATION_ATTACHED_DIALOG = FIRST_SUB_WINDOW+3; /** Window type: window for showing overlays on top of media windows. These windows are displayed betw..

m0_66144992的博客 272

数学建模模型总结

这是本人在两年内准备参加数学建模竞赛搜集到的模型资料,已经经过了本人的筛选和整理,希望能够对准备参加数学建模竞赛的学弟学妹们提供一些帮助!

NTscan扫描工具

ntscan是一个扫描器,可以扫描没有密码和弱密码的共享,先到配置文件中填写猜测的用户名和密码,扫描过程中右侧出现的是扫描日志。

Android WindowManager窗口类型,2021国内知名大厂Android岗面经

ZMS:OptionMenu、ContextMenu的默认类型 */ public static final int TYPE_APPLICATION_ATTACHED_DIALOG = FIRST_SUB_WINDOW+3; /** Window type: window for showing overlays on top of media windows. These windows are displayed between TYPE_APPLICATION_MEDIA and the.

m0_64382950的博客 610

Android入门之窗口类型

从WmS的角度看,一个窗口并不是Window类,而是一个View类。WmS收到用户消息后,需要把消息派发到窗口,View类本身并不能直接接收WmS传递过来的消息,真正接收用户消息的必须是IWindow类,而实现IWindow类的是ViewRoot.W类,每一个W内部都包含了一个View变量。         WmS并不介意该窗口(View)是属于哪个应用程序的,WmS会按一定的规则判断哪个窗口处

村长Korbin 1万+

26-Android之PhoneWindowManager中判断当前显示窗口类型

Android之PhoneWindowManager中判断当前显示窗口类型 在PhoneWindowManager中, 进行按键处理的时候, 有时候需要进行判断当前显示的窗口的类型. 通过PhoneWindowManager.mFocusedWindow进行判断进行判断 WindowState focusedWindow = mPhoneWindowManager.mFocusedWindow; Log.d(TAG, "isLauncher focusedWindow: " + focusedWindow)

陌上 802

Android 窗口类型

http://blog.youkuaiyun.com/forLittleBlue/article/details/59563755 WindowManager.LayoutParams.TYPE_PHONE:这是非应用窗口,提供与电话的用户交互(特别是来电)。 这些窗口通常放置在所有应用程序之上,但在状态栏后面,会被状态栏显示给覆盖,其他应用全屏时也会覆盖掉。放到状态栏区域显示时,它的点击、触摸事件会被

wangyang55555的专栏 530
上一篇: Android数据备份
下一篇: UML关系——泛化,实现,依赖,关联(聚合,组合)
leopard21
博客等级 码龄23年 25粉丝 56原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值